Recurrence not working after modifying the due date of a task

[aisneto]

• What command(s) did you run?

task add example due:15th recur:3d

== on January 17th ==

task *above task ID* mod  due:today

TaskWarrior would prompt a request if it should modify all following instances of this recurring task, which I entered "yes".

• What did you expect to happen?
  The child task would change it due date to today, and the template would be updated to spawn another child task 3 days from now, respecting the original recurrence with the new due date.

• What actually happened?
  Although the template task get updated, it does not spawn any more child instances.

Here is the task info:

Name            Value                                                
ID              16
Description   Shave beard                                         
Status          Recurring
Project         Hygiene
Recurrence      3d
Mask            ++++++
Recurrence type periodic
Entered         2023-12-23 14:01:44 (2w)
Waiting until   2023-12-24 00:00:00
Due             2024-01-07 00:00:00
Last modified   2024-01-08 07:30:39 (2d)
Virtual tags    MONTH PARENT PROJECT QUARTER TEMPLATE UNBLOCKED YEAR
UUID            d03dec67-de7f-44ab-87e2-017ed2dbcf42
Urgency         11.62

    project      1 *    1 =      1
    due      0.877 *   12 =   10.5
    age      0.049 *    2 =  0.099
                            ------
                             11.62

Date                Modification                                                
2023-12-23 14:03:08 Mask set to 'W'.
2023-12-24 15:44:39 Mask changed from 'W' to '+'.
2023-12-24 22:32:17 Mask changed from '+' to '+W'.
2023-12-28 09:48:43 Mask changed from '+W' to '+WW'.
2024-01-05 13:37:41 Mask changed from '+WW' to '+WWWW'.
2024-01-05 13:37:50 Mask changed from '+WWWW' to '++WWW'.
2024-01-05 13:37:50 Mask changed from '++WWW' to '+++WW'.
2024-01-05 13:37:53 Mask changed from '+++WW' to '++++W'.
2024-01-05 13:37:54 Mask changed from '++++W' to '+++++'.
2024-01-06 17:05:04 Mask changed from '+++++' to '+++++W'.
2024-01-08 07:30:27 Mask changed from '+++++W' to '+++++-'.
2024-01-08 07:30:31 Due changed from '2023-12-24 22:00:00' to '2024-01-07
                    00:00:00'.
2024-01-08 07:30:39 Mask changed from '+++++-' to '++++++'.

[tbabej]

What was the Taskwarrior version this behaviour was observed with? Perhaps the most easy would be to post the output of task diagnostics 🙂

[ElectricR]

Can confirm this.

It looks like changing the recur: attribute also breaks the task's recurrence cycle.

task diag

task 2.6.2 Platform: Linux

Compiler
Version: 12.1.0
Caps: +stdc +stdc_hosted +LP64 +c8 +i32 +l64 +vp64 +time_t64
Compliance: C++17

Build Features
CMake: 3.26.3
libuuid: libuuid + uuid_unparse_lower
libgnutls: 3.8.0
Build type:

Configuration
File: /home/er/.config/task/taskrc (found), 2388 bytes, mode 100644
Data: /home/er/.local/share/task (found), dir, mode 40755
Locking: Enabled
GC: Enabled
$EDITOR: kak
Server:
CA: -
Certificate: -
Key: -
Trust: strict
Ciphers: NORMAL
Creds:

Hooks
System: Enabled
Location: /home/er/.config/task/hooks
Active: on-modify.timewarrior (executable)
Inactive:

Tests
Terminal: 547x127
Dups: Scanned 5546 tasks for duplicate UUIDs:
Found duplicate 90cc89aa-1b0f-47d1-888f-4e9ca3616dff
Broken ref: Scanned 5546 tasks for broken references:
No broken references found

[djmitche]

@carmiac has proposed a major revision to recurrence support in https://github.com/carmiac/taskchampion/blob/798cec2b40f13c420ef6358e4d99b251e58249de/docs/src/iterative-tasks.md. If you're following this issue, please have a look and comment in GothenburgBitFactory/taskchampion#729.