Currently, when using recurrence, the "Until" field determines when the recurrance stops. Take this example from the taskwarrior docs
task add Pay the rent due:1st recur:monthly until:2015-03-31
Created task 123.
This will make a task "Pay the rent" which will recur monthly, and stop recurring on 2015-03-01. This is great functionality, however it prevents creating any recurring tasks where the task instances themselves need to have an until date.
For example, if I want the task
task add "Put the garbage out" due:sunday recur:weekly
I would likely want that task to expire after a week, so I can have the next weeks garbage task instead.
If I try to do this
task add "Put the garbage out" due:sunday recur:weekly until:due+6d
This will make the task stop recurring after one week, which is unintended.
Is this something that can be separated out somehow?
Currently, when using recurrence, the "Until" field determines when the recurrance stops. Take this example from the taskwarrior docs
This will make a task "Pay the rent" which will recur monthly, and stop recurring on 2015-03-01. This is great functionality, however it prevents creating any recurring tasks where the task instances themselves need to have an until date.
For example, if I want the task
I would likely want that task to expire after a week, so I can have the next weeks garbage task instead.
If I try to do this
This will make the task stop recurring after one week, which is unintended.
Is this something that can be separated out somehow?