Linking SCHEDULED and DEADLINE repeating timestamps to avoid desynchronization

Linking SCHEDULED and DEADLINE repeating timestamps to avoid desynchronization

[J. G.]

[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]

Hi everyone, I just stumbled across a surprising behavior with combined SCHEDULED and DEADLINE timestamps that repeat. Here is the example org file contents:
* TODO My late recurring todoSCHEDULED: <2023-04-12 Wed ++1w> DEADLINE: <2023-04-13 Thu ++1w>
Right now it is Wednesday (2023-04-26 to be precise), and as shown above, my task had a scheduled timestamp on a Wednesday from a previous week. The repeater is ++1w, so marking the task as done bumps it to repeat on Wednesday of next week (2023-05-03 to be precise). That functions as expected.
But the deadline timestamp is on a Thursday of a previous week with a repeater of ++1w, so marking the task as done bumps it to Thursday of this week (2023-04-27 to be precise). So marking it as done it has the logical but unexpected result of having the scheduled timestamp for a date (2023-05-03) after the deadline timestamp (2023-04-27).
Is there a way to link the timestamps so that marking the task done will always bump the deadline timestamp after the scheduled timestamp? On the IRC channel I was kindly directed to look into org-todo-repeat-hook as a way to approach it, but to share this here in the mailing list as an edge case to be considered.

[-- Attachment #2: Type: text/html, Size: 1547 bytes --]

[BUG] Linking SCHEDULED and DEADLINE repeating timestamps to avoid desynchronization

[Ihor Radchenko]

"J. G." <jerzor@pacbell.net> writes:

> * TODO My late recurring todoSCHEDULED: <2023-04-12 Wed ++1w> DEADLINE: <2023-04-13 Thu ++1w>
> Right now it is Wednesday (2023-04-26 to be precise), and as shown above, my task had a scheduled timestamp on a Wednesday from a previous week. The repeater is ++1w, so marking the task as done bumps it to repeat on Wednesday of next week (2023-05-03 to be precise). That functions as expected.
> But the deadline timestamp is on a Thursday of a previous week with a
> repeater of ++1w, so marking the task as done bumps it to Thursday of
> this week (2023-04-27 to be precise). So marking it as done it has the
> logical but unexpected result of having the scheduled timestamp for a
> date (2023-05-03) after the deadline timestamp (2023-04-27).

Confirmed.
I think it makes sense to have a special case for scheduled and
deadlines, making sure that they shift by the same number of days in
future, when their repeaters are the same.

However, I do not think that it should be done for all other timestamps
under heading.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Re: [BUG] Linking SCHEDULED and DEADLINE repeating timestamps to avoid desynchronization

[J. G.]

[-- Attachment #1: Type: text/plain, Size: 1960 bytes --]

 Thanks for confirming the issue.
For the record, after doing some more research it looks like at least one other person came across this issue, and the workaround was using org-edna in place of the repeaters, which will push the timestamps together to the same date offset prior to the scheduled-deadline date range, and then increment them forward to the correct dates:
Use Edna Instead of the Repeater Pattern · Konubinix' Site


| 
| 
|  | 
Use Edna Instead of the Repeater Pattern · Konubinix' Site


 |

 |

 |





    On Thursday, April 27, 2023 at 04:28:11 AM PDT, Ihor Radchenko <yantar92@posteo.net> wrote:  
 
 "J. G." <jerzor@pacbell.net> writes:

> * TODO My late recurring todoSCHEDULED: <2023-04-12 Wed ++1w> DEADLINE: <2023-04-13 Thu ++1w>
> Right now it is Wednesday (2023-04-26 to be precise), and as shown above, my task had a scheduled timestamp on a Wednesday from a previous week. The repeater is ++1w, so marking the task as done bumps it to repeat on Wednesday of next week (2023-05-03 to be precise). That functions as expected.
> But the deadline timestamp is on a Thursday of a previous week with a
> repeater of ++1w, so marking the task as done bumps it to Thursday of
> this week (2023-04-27 to be precise). So marking it as done it has the
> logical but unexpected result of having the scheduled timestamp for a
> date (2023-05-03) after the deadline timestamp (2023-04-27).

Confirmed.
I think it makes sense to have a special case for scheduled and
deadlines, making sure that they shift by the same number of days in
future, when their repeaters are the same.

However, I do not think that it should be done for all other timestamps
under heading.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

  

[-- Attachment #2: Type: text/html, Size: 6163 bytes --]