Choose where recurring tasks start

Choose where the next recurring task starts. The recurrence controls now include New tasks start in, with eligible columns from the project workflow. Changing this setting keeps the current task in its column.

Keep the series destination current

Completion and scheduled recurrence use the saved destination. After you move a recurring series, historic tasks stay in their projects. Completing an older occurrence creates the next task in the series’ current project and selected column. Scheduled occurrences continue to appear through the maintenance sweep.

The project default is Todo when available, or the first nonterminal column. A target change keeps the schedule clock and cadence. Disabling recurrence clears its target.

Use the same controls through agent tools

REST and CLI accept nullable recurrence targets. Existing MCP issue tools expose completion recurrence and its target in both profiles. Reads show the stored task target separately from its authorized series owner; inaccessible owners reveal no identifiers.

Column deletion can remap current task statuses, dependency release points, and recurring targets independently in one atomic request. CLI and MCP deletion require explicit confirmation. If a deletion response is uncertain, read the workflow before sending another request.