DEV Community

hiro@
hiro@

Posted on Originally published at qiita.com

Plane recurring work needs two checks: the next instance and unfinished earlier work

Automatically creating this week's maintenance task does not finish last week's check. When adopting Plane Recurring Work Items, define both the next instance's scope and how unfinished earlier instances will be handled.

This is a configuration proposal based on official documentation checked on September 11, 2026. No recurring pattern was created, and no following week's automatic creation was observed. A reduction in forgotten maintenance has not been measured.

The recurring unit is a task template

The Recurring Work Items reference describes a template that creates new work on a schedule. It is not treated here as repeatedly resetting an existing Done item to Todo.

The page carries a Business label. Its setup path is Project Settings, then Recurring work items, with content, assignees, start/end dates, and daily, weekly, monthly, or yearly frequency. Availability in the target subscription remains a check in that environment.

Define what completes one instance before choosing its frequency. A title such as maintenance does not say which evidence is sufficient to close it.

Give a dependency review a narrow completion condition

Consider a weekly task to review dependency-update candidates. Combining investigation with implementation can leave a large update overlapping the next scheduled task.

The proposed description contains:

Target repository and reference commit:
Official information checked and review date:
Changes requiring action and supporting evidence:
Reason when no action is needed:
Links to follow-up work:
Enter fullscreen mode Exit fullscreen mode

Completion means investigating candidates and recording the result. An update needing implementation or release should receive its own scope and verification conditions. Closing the recurring review would not claim that implementation is complete.

A no-change week still records the review date and inspected versions. An empty field cannot distinguish a completed check from an item that was merely opened. This proposal has not been tested through ongoing weekly operation.

Different maintenance work has different timing

Candidate Check in the recurring item Manage separately
Dependency updates New releases and changes Implementation, compatibility checks, delivery
Certificates Expiry and renewal path Required action before actual expiry
App stores Required declarations and policy changes Submission deadlines and review responses
Article publishing Planned publication versus recorded outcome Publication itself and recovery from failure

This table does not propose one frequency for everything. A certificate's expiry or store deadline is distinct from the weekly review date. Creating a task weekly does not guarantee timely action.

No external update, declaration, or publication was performed. The proposal organizes work for a person to inspect; it does not create a scheduler that executes those operations automatically.

Editing the template leaves earlier instances to resolve

The documentation says recurring-template edits affect future work items, leaving already-created instances unchanged. Adding a review field should therefore not be assumed to update last week's description.

This local ledger illustrates the distinction. It is not a record of instances generated by Plane:

Instance date Description version Work status Review record
2026-09-11 v1 Awaiting review Missing
2026-09-18 v2 Not started Missing

Improving the next description leaves the earlier result missing. Completing the earlier review, transferring its remaining scope, or closing it because it is no longer needed requires a separate decision. A later instance's existence does not justify marking its predecessor Done.

When turning a one-time activity into recurring work, decide when new instances should begin rather than assuming the past will be filled in. Backfilling, execution time, and timezone behavior were not verified here.

Define the adoption checks before enabling recurrence

Inspect the first generated item's name, assignee, description, and project. On the next occurrence, verify that it is a separate work item and locate the previous unfinished work. After changing the description, check which occurrence first uses the new version.

These steps remain for adoption. The work here checked the documented creation and edit behavior and prepared a dependency-review description with an unfinished-instance ledger. The local proposal preserves both; its JSON is not a Plane API payload.

If only manual reuse of content is needed, Work Item Templates is another option. Distinguish content reuse from scheduled creation, then evaluate the resulting review evidence and remaining work after adoption instead of merely counting generated tasks.

Top comments (0)