Skip to content

feat: let recurring tasks follow the status cycle on click - #2492

Merged
callumalpass merged 5 commits into
callumalpass:mainfrom
martin-forge:martin-forge/recurring-status-click-cycle
Nov 3, 2026
Merged

callumalpass merged 5 commits into
callumalpass:mainfrom
martin-forge:martin-forge/recurring-status-click-cycle

Conversation

@martin-forge

@martin-forge martin-forge commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Problem

Clicking a task card's status icon moves an ordinary task to its next status, but completes a recurring task's occurrence straight away. On a board with both, the same click starts one card and finishes another, so a recurring task can't be clicked into In progress. #1370 asked for recurring tasks to cycle like other tasks.

Solution

The status icon now does the same thing on every card. A recurring card follows the status cycle, and reaching Done completes the occurrence shown. A completed occurrence still reopens on click.

This applies when the first completed status has a Next status, the status a finished series starts its next occurrence in (#2441). Without one, the series would carry In progress into its next occurrence, so the click still completes the occurrence directly.

The built-in Done status now moves on to Open, so new setups get the same behaviour on every card, and reopening a finished task returns it to Open rather than None. Saved statuses aren't changed.

Testing

Unit tests and two Kanban tests in Obsidian cover the cycle and the one-click fallback. The cycling test fails on main and passes here. All repo checks pass locally.

@callumalpass
callumalpass merged commit 245062f into callumalpass:main Nov 3, 2026
3 checks passed
@callumalpass

Copy link
Copy Markdown
Owner

Thanks @martin-forge, merged. This closes the gap between recurring and ordinary tasks that @Jomo94 raised in #1370, and building on your #2441 work kept the change small. I pushed a small follow-up to the release note and docs to warn people who already have a Next status set on Done, and moved the spec to e2e/issues/.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants