Comment 64 for bug 307680

(In reply to comment #18)
> If we would be creating exceptions for each completed task, then the calendar
> would get quite large only due to completed tasks.

How much of a problem is the size of the calendar due to completed tasks? Right now, the only way to implement repeating tasks is to create a separate task for each occurrence, so fixing this bug should produce a decrease in the size of the calendar (it would only need to store past completed occurrences, not every occurrence).

(In reply to comment #18)
> Also, editing a once completed task would not modify the whole series but the
> exception.

If I want to effect the whole series, I would modify the future tasks, not the already completed tasks. When I make a change to future (or uncompleted) occurrences, I generally want that change to effect all future occurrences, but I don't want that change to effect completed tasks. In the rare case that I modify an already completed task, I don't think I would want that change to effect all future occurrences.

This is the way that Outlook behaves, once a task is completed it is completely isolated from the remainder of the occurrences. I think it is kind of intuitive.

(In reply to comment #18)
> If we set an X-Prop similar to alarms that all tasks after date N are
> completed, this wont be portable any time in the future and its not possible to
> have last weeks occurrence not completed but this weeks occurrence completed.

Perhaps an X-Prop could be created that lists which occurrences of the task have been completed?
I'm not familiar with X-Props, but if the same X-Prop can exist multiple times in a single task, maybe each completed occurrence can create a new entry that says which occurrence was completed and when it was completed?

(In reply to comment #18)
> Also its unclear how the completed state on the item itself should be.

If you go with the X-Prop approach, the completed state on the item itself would be pretty much ignored. However, I suppose it could indicate whether all occurrences of the task are completed (basically as it behaves now).

(In reply to comment #18)
> I'd personally like to have working recurring tasks too, but its not easy to
> find a working concept here, as you see that other applications don't
> implement it at all :-)

There are at least a few applications that do implement repeating tasks (RTM and Microsoft Outlook are the two that come to my mind). Are there any applications that support both ICS and have a good implementation of repeating tasks?

Also, is there a place to discuss possible implementations (a wiki page perhaps), or is this bug the place?