Jan Stolarek on 2018-02-03T17:25:04Z says:
I have a bunch of tasks that I want to recur on a monthly basis. On the 2nd December I created two such tasks:
`$ task add "Create backup" recur:1month due:3d
Created task 13 (recurrence template).
$ task add "Pay the bills" recur:1month due:3d
Created task 13 (recurrence template).`
Now on the 3rd December I completed one of them:
3nd December:
$ task 16 done Completed task 16 'Create backup'. Completed 1 task.
On the 6th December new instances of each task have been spawned:
`$ task
ID P Due Time Description
17 M 5-12-2017 22h Pay the bills
19 M 4-01-2018 Create backup
20 M 4-01-2018 Pay the bills`
There is now one instance of "Create backup" and two instances of "Pay the bills". New instances will be due in a month so I put them on a waiting list:
`$ task 19-20 mod wait:eom
Modifying task 19 'Create backup'.
Modifying task 20 'Pay the bills'.
Modifying recurring task 17 'Pay the bills'.
Warning: You have specified that the 'wait' date is after the 'due' date.`
At some point I also mark task 17 as done. I admit I have not precisely reporduced my every usage of task during the month of December but on the 6th of January I realized I have the following waiting tasks:
`$ task waiting
ID P Project Wait Remaining Due Description
14 M 30-01-2018 3w 30-01-2018 Create backup
15 M 30-01-2018 3w 30-01-2018 Pay the bills
25 M 1-03-2018 7w 3-02-2018 Create backup
27 M 1-03-2018 7w 3-02-2018 Pay the bills`
Notice two bogus instances with wait times set to March and due dates for February. I have marked those two tasks as done on 31st January and also marked tasks 14 and 15 as done. On the 31st January I already had new instances of my recurring tasks spawned:
`$ task waiting
ID P Project Wait Remaining Due Description
14 M 28-02-2018 3w 28-02-2018 Create backup
15 M 28-02-2018 3w 28-02-2018 Pay the bills`
On the 3rd another instances were spawned:
`$ task waiting
ID P Project Wait Remaining Due Description
14 M 28-02-2018 3w 28-02-2018 Create backup
15 M 28-02-2018 3w 28-02-2018 Pay the bills
25 M 1-04-2018 3w 5-03-2018 Create backup
26 M 1-04-2018 3w 5-03-2018 Pay the bills`
Notice the nonsense wait and due dates for new tasks.
This problem did not happen with older versions of Taskwarrior. I don't remember whether this started happening when I switched from 1.9 to 2.0 or from 2.0 to 2.5, but the fact is that something goes wrong with spawning recurring tasks and every few months I just have to delete all of them and create them anew because they become such a mess. Ot seems like there are two copies of the same task being spawned and something bad is happening with "due" dates ("wait" dates as well?). Sorry, I know this is a bit vague but this is the best description I can provide for the moment.
Jan Stolarek on 2018-02-03T17:25:04Z says:
I have a bunch of tasks that I want to recur on a monthly basis. On the 2nd December I created two such tasks:
`$ task add "Create backup" recur:1month due:3d
Created task 13 (recurrence template).
$ task add "Pay the bills" recur:1month due:3d
Created task 13 (recurrence template).`
Now on the 3rd December I completed one of them:
3nd December:
$ task 16 done Completed task 16 'Create backup'. Completed 1 task.On the 6th December new instances of each task have been spawned:
`$ task
ID P Due Time Description
17 M 5-12-2017 22h Pay the bills
19 M 4-01-2018 Create backup
20 M 4-01-2018 Pay the bills`
There is now one instance of "Create backup" and two instances of "Pay the bills". New instances will be due in a month so I put them on a waiting list:
`$ task 19-20 mod wait:eom
Modifying task 19 'Create backup'.
Modifying task 20 'Pay the bills'.
Modifying recurring task 17 'Pay the bills'.
Warning: You have specified that the 'wait' date is after the 'due' date.`
At some point I also mark task 17 as
done. I admit I have not precisely reporduced my every usage of task during the month of December but on the 6th of January I realized I have the following waiting tasks:`$ task waiting
ID P Project Wait Remaining Due Description
14 M 30-01-2018 3w 30-01-2018 Create backup
15 M 30-01-2018 3w 30-01-2018 Pay the bills
25 M 1-03-2018 7w 3-02-2018 Create backup
27 M 1-03-2018 7w 3-02-2018 Pay the bills`
Notice two bogus instances with wait times set to March and due dates for February. I have marked those two tasks as done on 31st January and also marked tasks 14 and 15 as done. On the 31st January I already had new instances of my recurring tasks spawned:
`$ task waiting
ID P Project Wait Remaining Due Description
14 M 28-02-2018 3w 28-02-2018 Create backup
15 M 28-02-2018 3w 28-02-2018 Pay the bills`
On the 3rd another instances were spawned:
`$ task waiting
ID P Project Wait Remaining Due Description
14 M 28-02-2018 3w 28-02-2018 Create backup
15 M 28-02-2018 3w 28-02-2018 Pay the bills
25 M 1-04-2018 3w 5-03-2018 Create backup
26 M 1-04-2018 3w 5-03-2018 Pay the bills`
Notice the nonsense wait and due dates for new tasks.
This problem did not happen with older versions of Taskwarrior. I don't remember whether this started happening when I switched from 1.9 to 2.0 or from 2.0 to 2.5, but the fact is that something goes wrong with spawning recurring tasks and every few months I just have to delete all of them and create them anew because they become such a mess. Ot seems like there are two copies of the same task being spawned and something bad is happening with "due" dates ("wait" dates as well?). Sorry, I know this is a bit vague but this is the best description I can provide for the moment.