555596 - Recurring tasks do not have a due date.

Status: RESOLVED WORKSFORME

(Calendar :: General, enhancement)

Description

[Gregory Tetrault]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 GTB6
Build Identifier: Lightning 1.0b1

Recurring tasks get a start date but no due date. The due date should be the next scheduled occurrence. Once the task for that due date is marked complete, the due date should be updated to the future. Example Task: Backup disk every Sunday at 9:00 starting today (3/28/10). Once I mark it as completed, the due date should change to 4/4/10 at 9:00.

Reproducible: Always

Steps to Reproduce:
Not relevant
Actual Results:  
Not relevant

Expected Results:  
Not relevant

Take a look at Entourage to see how it handles recurring tasks.

Comment 1

[Graham P Davis]

I would have agreed completely with these comments this morning but I've just checked again and, in the Calendar display, each occurrence of a task has a different due date appropriate to the date it appears in the calendar. However, the situation is complicated by the Calendar display behaving totally differently to the Tasks displays.

I have tasks that are marked as complete in the calendar display up to and including the whole of this month (April). However, the task displays say they "need action" and the "due dates" are for March - that's the first occurrence of these tasks.

A probable related problem showing the differences between operating in Calendar or Tasks is that, in Calendar, if I select a recurring task for editing, I can choose whether to edit a single occurrence or all. In Tasks however, the only effect of editing a task is to change all occurrences. Thus, marking an occurrence as complete, marks all subsequent occurrences of the task as complete. This suggests to me that in Tasks, a recurrent task has only one due date, similar to the complaint by Gregory, but somehow works as intended in Calendar.

I've not used Entourage but have used the Kontact PIM in KDE. Do NOT bother looking at that!

Comment 2

[Stefan Sitter [:ssitter]]

Graham, all your experiences can be explained by Bug 350174.

Comment 3

[Lasana Murray]

This seems to be working to me.