Yes, that's correct Jeffrey. The various automatic triaging (button
triaging and section triaging) options are never mutually exclusive.
Sharing and Edit/Update changes to an item affect the
sectionTriageStatus of that item. However that does not preclude
other automatic triage operations from having their way with the item.
If the change was a change to the item's date/time, then auto-
triaging based on date/time changes should also take effect.
Apologies for not making that more clear earlier and thanks for
catching this important use case.
Mimi
On Mar 1, 2007, at 12:18 PM, Jeffrey Harris wrote:
Hi,
Bryan Stearns is working on a million different triage things, I'm
working on the triage bits relating to recurrence. We've hit a
spot in
the spec where we're interpreting things differently, we'd like
more input:
-----
Automatic operations affecting triage status:
...
* When items are newly received or updated via sharing or mail, if
this user's "Share triage status" choice is off in all collections
this
item belongs to:
o (These changes only affect item sort order, not button
color; if the item had a pending unpurged sectionTriageStatus
pinning it
in place, this overrides it. When the next "Triage" purge happens, the
item will move to the position determined by the triage status
originally set by the local user.)
o The item is moved to the top of the NOW section.
o The item is marked "unread".
-----
I'm thinking "These changes only affect item sort order, not button
color" doesn't include the case where an event's date is changed. In
that case, I think the item should move to the NOW section *and* it
should be auto-triaged. Can we clarify that case?
Sincerely,
Jeffrey
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
