Hi Dan, > Currently the display order of summary table rows can change > immediately after a user completes an edit on an item. I think this > is undesirable behavior. I think the table view should only re-order > when the column headers are clicked, or in response to the passage of > time.
I'd be happy with changing this behavior, from a usability perspective, but I'll note that I think implementing such a feature would be non-trivial. Personally, I never bump into this because I never sort on anything except triage status, but that's just me. > 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. The problem with this is that the triage button is important to sharing workflows. If you're viewing items sorted by title and you get new inbound items, you don't want to click on sort by triage and lose the information that there were inbound changes to a later item. I'd be happy to rename the Triage button Re-sort, though. There was feedback today at our usability sprint that "triage" isn't a generally understood word so we should at least add a tooltip, or consider renaming the button. Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
