It works great! Noticed it coming into play last Friday/Saturday. Bryan, love it!
This first level triage concept (Now, Later, Done) is an excellent front-end to GTD in a message intensive environment. Great to have it implemented further. One design thought that has already come to mind is the notion of "past due". I have already had items stamped simultaneously as Tasks and Events that the auto-triage function has marked Done after the date/time went by, as expected. However, I wasn't actually "done" with the task. (Chandler was a bit optimistic about my personal productivity.) In my point of view, the item was Past Due, but not yet Done. Seems to me this might be a potential triage status type. Perhaps this scenario/notion is already catalogued for future treatment? Andre On Mon, 19 Mar 2007 14:31:59 -0700, "Jeffrey Harris" <[EMAIL PROTECTED]> said: > Hi Folks, > > After long hard work, last week Bryan Stearns got the recurrence-triage > branch passing all tests and merged into the main codebase today. Yay! > > There are a variety of triage-related behavior changes in Chandler as of > r13478. A surely-not-exhaustive list of features: > > Auto-triage > =========== > > Imported and new items are auto-triaged. This means if you create an > event using quick entry by entering: > > /event Lunch tomorrow with Dorothy and Toto > > You'll get an event tomorrow at noon, as usual, but now that event will > be triaged LATER. It will still be sitting in your NOW section waiting > to be accepted, though, so if you mostly just look at your NOW section > you'll get a chance to confirm that noon was the time you wanted. > > Moving events > ============= > > If you move a DONE event from some time in the past to the future, its > triage status will automatically change from DONE to LATER. > > One subtle exception to the above rule is that if you've explicitly > changed the triage status for an item, it won't be auto-triaged to > LATER, it'll stay how you set it. Similarly, if the event's start time > arrives or a reminder fires for an item, once Chandler automatically > changes the triageStatus to NOW, changing its start time won't change > its triage status again. > > Recurrence and triage > ===================== > > Recurring events continue to show up as several rows in the dashboard > view (one for done, one for later), but there's no longer a permanent, > special row for the first occurrence. > > When you add recurrence to an event, the first occurrence stays selected > and in the same section of the dashboard, so the event shouldn't > disappear on you when you add recurrence. > > The first occurrence stays in place until the triage button is pressed. > When triage is pressed, in addition to moving all your items to the > appropriate section (the old behavior for the triage button), the most > recent DONE event and the nearest future LATER event is kept. Other > occurrences (including the first occurrence) are removed from the table, > to reduce clutter. > > The exception to THIS rule is that, if you've made any non-triage > changes to an event, the event will stick around in the table view. > > To give a more concrete example, if I make an event using quick entry: > > /event Examined the yellow brick road last month > > I'll have a DONE event starting last month that shows up in the NOW > section. Now, if I add weekly recurrence, I'll see three events: > > NOW section: > last month, DONE > LATER section: > later this week, LATER > DONE section: > last week, DONE > > If I press the triage button, last month's DONE event goes away. But if > first, I change the title of the first event to "Yellow brick road > examination cancelled due to rain", after triage is pressed, last > month's event will move to the DONE section, instead of disappearing. > > Give it a try! > > 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
