Cyclic Tasks > Comment

good points! / #5398

EditBookmarkDelete
> 3. Efforts
it would be perfectly alright for me to be able to sum up the efforts for tasks inside one folder, because thats where they should live imho

i thought a while about this. it ends up the questions "when is a new task created" and "how are the new dates calculated

1 no date calculation

for now an easy solution might be like this:
  • a task has a recurring property
  • when i finish the task, i get a task edit view pre-populated with a copy of the current one
  • i set the new start and end date manually

1a simple overridable date calculation

for now an easy solution might be like this:
  • a task has a recurring and a offset property
  • when i finish the task, i get a task edit view pre-populated with a copy of the current one, shift by offset
  • if necessary i set the new start and end date manually

2 fixed but overridable repeat intervals

  • a task has a recurring property
  • when i finish the task, or when end-date expires, a new copy of the actual task is created as follows:
    • start date and end date are incremented by repeat-after.
    • if next-on property is given, an appropriate offset is added to start date and end date, so that start date equals next-on (edit: we should be able to choose if this applies to start or end date)
    • the new copy has the same repeat-after, but no next-on
    • the recurring of the actual task is set to false

3. the bells-and-whistles-solution

we would have to provide a full-blown "recurring events" interface like the ical calendars do. perhaps we could get a library from projects like egroupware or so.

my proposal

for me solution 1 would be a good start: if i dont have solution 3 (which is far away imho) i have to think about the next dates anyway.
for example with monthly press releases which are due to every 10.: i might set a 30-day offset, but would have to correct this anyway.