[TW-150] Create recurrences based on end dates in addition to due dates

[taskwarrior]

Cory Donnelly on 2010-07-28T17:24:45Z says:

Sometimes the only concern a user has about a scheduled recurring task is that it shouldn't be sooner than x number of days since the last occurrence was completed. Consider the current recurrence scheme, based on due date:

$ task add due:2010-09-01 Call mom
Using alternate .taskrc file minimal.rc
Created task 3.
$ task recur:monthly 3
Task 3 is now a recurring task.
Using alternate .taskrc file minimal.rc
Modified 1 task.

Now, if the user were to call his or her mom half a month early, then the next recurrence wouldn't be for another 1.5 months.

[taskwarrior]

Migrated metadata:

Created: 2010-07-28T17:24:45Z
Modified: 2016-04-29T06:36:54Z

[taskwarrior]

Cory Donnelly on 2010-08-15T08:49:56Z says:

I'm finding that more and more of my obligations are best modeled using this period-dependent (versus due date dependent) type of recurrence:

• Check backup tapes
• Get a haircut
• Water plants
• Bathe the dog
• Call mom
• Mow the lawn
• Get an oil change

Implementing this means that:

• future child tasks can't be created until the previous child task is marked as completed
• consequently, (at)rc.recurrence.limit@ can't be used for these

[taskwarrior]

Paul Beckingham on 2010-08-15T08:55:58Z says:

I think you've found a new species of recurrence.

It is similar to the current species, but the subsequent task is only scheduled when the first is dismissed. RFC?

[taskwarrior]

Cory Donnelly on 2010-08-15T12:21:48Z says:

Paul Beckingham wrote:

I think you've found a new species of recurrence.

It is similar to the current species, but the subsequent task is only scheduled when the first is dismissed. RFC?

Agreed, I'm working on rfc32-recurrences.txt which discusses features #448 and #456.

[taskwarrior]

Federico Hernandez on 2010-08-15T14:56:25Z says:

Paul, at some point there was a discussion about these type of recurrances, IIRC. But I don't know if we did that via email or on IRC. would be useful for you, Cory, if we could dig it up.

[taskwarrior]

John Florian on 2010-08-22T11:25:28Z says:

This is functionality that has great interest to me as well. I have about an equal split of tasks of the "normal kind" and those that are preventive maintenance. Oil changes are definitely preventive and as stated above need to essentially be rescheduled upon completion of the most recent.

Some are harder to pin down. Consider my task for buying and adding salt to the water softener. I've got a solid calculation down for the usage rate and can accurately predict when it'll be needed (at the latest). Our standard recurrence model works perfectly so long as I replenish the salt before the due date. After that the schedule is permanently slipped.

So I'm not sure if this is something that should be fixed in stone when the task is created. Perhaps task could ask what to do when an ID is completed. Maybe task does something special just because it is after the due date. Thoughts?

[taskwarrior]

Daniel Shahaf on 2015-10-19T01:15:59Z says:

Is this a duplicate of TW-1314 and TW-235?

[taskwarrior]

Paul Beckingham on 2015-10-19T04:48:49Z says:

Yes, duplicates - thanks. Closed the others, keeping the original.

[taskwarrior]

Scott Kostyshak on 2016-04-29T06:36:54Z says:

Are TW-1774 and TW-1751 both duplicates of this one?

[jcrben]

Seems like https://github.com/JensErat/task-relative-recur helps with this use case?