Option for recurring tasks to still recur when cancelled

[ElleryXii]

⚠️ Please check that this feature request hasn't been suggested before.

• I searched previous Ideas in Discussions didn't find any similar feature requests.
• I searched previous Issues didn't find any similar feature requests.
• I am only requesting a single feature. Multiple changes should be split into individual requests, with links between them.
• I believe my requested feature will be generally applicable to other users, not just me: it is not uniquely tied to my personal workflow.

🔖 Feature description

I would like an option to make recurring tasks still create new instances when cancelled.

✔️ Solution

This could be a global toggle for all recurring tasks or an additional syntax for individual tasks. Once enabled, the recurring task should create a new instance as usual when it's cancelled.

This is helpful for most of the use cases mentioned in #2053, but without the need for batch processing (i.e., it does not happen without user interaction). Generally speaking, many optional/routine tasks may be cancelled on any given day but still need to recur regardless.

❓ Alternatives

From the comment in #1855, I understand the intended way to skip a recurring task is to mark it as complete first to create a new instance, then mark the just completed instance as cancelled. However, this may be impractical when interacting with query results. For example, I set up my daily tasks in my quarterly plan, and only query for incomplete scheduled tasks in my daily notes. Once an instance is marked as cancelled, it disappears from the queried result and I'd need to go to the quarterly plan to modify it, which defeats the purpose. I considered adding a query for cancelled tasks in the daily notes purely for this interaction, but ultimately it's not ideal.

Another alternative is to make a custom "DONE" status (say, "Skipped"). I think it technically works, but makes querying for all cancelled tasks cumbersome and can be visually confusing.

📝 Additional Context

This might make stopping recurring tasks less straightforward. However, it may be reasonable to make a one-time operation (stop recurrence) slightly less convenient in favour of an operation that might happen often during a task's life span.

[evcraddock]

Having a skipped status would allow us to build a monthly reports using something like dataview. We could have a better understanding of how often a recurring status didn't happen. As it is clicking Cancelled cancels the rucurring task and clicking done invalidates reporting.

[claremacrae]

Just to note an idea....

As more context menus get added to Tasks, I think the best way of implementing this would be to add a right-click context menu on the Recurrence emoji, and include an option called something like:

• 'Cancel this recurrence and create the next one'

Confusingly, it would change the meaning of when done to effectively when done or when instance is cancelled...

Having a context menu is going to be better both for users and for maintainers than having to add extra settings, or extra options on parse on the task line...