[Design] Should dashboard display order change immediately after edits?

[Keith Winsor]

Dan Steinicke wrote:
> I think this also ties in to the end user confusion around the 
> "Triage" button.  I have always thought it would be much more 
> intuitive to just have the triage column header button do what the 
> "Triage" button now does.  In my understanding the main function of 
> the "Triage" button is to prevent row reordering when you change the 
> triage state.  If rows only re-ordered when the headers were clicked 
> then it would seem we would be able to simplify this work flow as 
> well.        Are there users out there who like the automatic 
> re-ordering in response to edits? Are there users out there who are 
> annoyed by the dashboard re-ordering in response to edits?     
> Dan  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Dan,

I agree re automatic sorting making it confusing to keep track of items.

I'm not so sure about 'simplifying' the Triage button. I've noticed 
(i.e. this method of usage has crept up on me and your post has made me 
realise how I do it!) that I tend to make triage decisions in the Now 
section on a screenful of items at a time, then triage to dispose of the 
Dones and Laters I've just marked, before dealing with the next batch. I 
guess it gives me my instant gratification in more manageable chunks! It 
occurs to me that if someone has amended a shared Later event (which 
pops into Now as a result) that by doing this I might miss the event 
unless it shows up on the first page of Nows, and triage it unseen back 
to Later, so maybe I should just change my usage pattern, in which case 
using headers would be a viable solution. But I think the triage button 
is a bit of a USP of Chandler and genuinely gives you that 'I've 
achieved all of this' feeling, where clicking on a column header 
doesn't. So objectively I agree but subjectively I disagree!

Any other users out there with odd Chandler habits?

Keith