Hi Mimi, > There is also the issue of triaging and marking recurring events as > read/unread/needs reply, also pasted below. Jeffrey, are we really > applying explicit triaging to the entire series? I couldn't remember if > we only agreed to do that with Read/Unread/Needs reply status or if we > are doing that with Triage as well.
I think triage status should continue to apply to individual occurrences. There's fairly elaborate code to make triage status per-occurrence based on start time, making triage changes apply in a different way would be a lot of design back and forth and implementation time. > *Also...the stuff in the Triaging/Marking as Read/Unread section, should > the same rules apply to Stamping to Add to/Remove from Task list and > Adding/Removing Reminders? Both can be done from the Dashboard.* Currently we only allow stamping as a task to apply to individual occurrences. That was before the recurrence branch landed, I think it would be reasonable to allow either now, but at least in the dashboard, I'm happy with the task stamp always applying to individual occurrences. Reminders added through the dashboard are absolute reminders. Right now you can't add a reminder to a recurring event through the dashboard, that's bug 8214. When you can, I'd say that to be consistent we should add an absolute reminder to individual occurrences, not make reminder changes apply to all occurrences. Setting a later 5PM/8AM absolute reminder when looking at an occurrence just seems like a one off behavior, not something likely to apply to all occurrences. Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
