Community
Participate
Working Groups
"mark as read and move to next unread" action should be discoverable trough popup menu in the task list (next to mask as read)
This action is intentionally not visible in any menu. It is considered to be advanced and it is not clear if it will be supported in future versions.
*** Bug 219189 has been marked as a duplicate of this bug. ***
Hmm. (In reply to comment #1) > This action is intentionally not visible in any menu. It is considered to be > advanced and it is not clear if it will be supported in future versions. Can you please clarify considered by whom? This is one of the usability features that actually makes Mylyn better then the web UI. Hiding such usability gems from the end users is not exactly helpful. Also note that most popular email readers provide equivalent of "go to next unread" action.
Mylyn strives to keep its UI simple. This action is very advanced and combines two operations - changing state and navigating - in one command. My sense is that this is more confusing than helpful to most users. I would prefer to put effort towards fixing bug 208923 which was the motivation to have this advanced command instead of overloading the UI. > This is one of the usability features that actually makes Mylyn better then the > web UI. Hiding such usability gems from the end users is not exactly helpful. > Also note that most popular email readers provide equivalent of "go to next > unread" action. Yes, that's why I support having advanced actions in Mylyn but that doesn't mean the UI needs to expose all advanced functionality in prominent places. Please note that go to "Next Unread Task" action is discoverable through the Navigate menu.
(In reply to comment #4) > Mylyn strives to keep its UI simple. This action is very advanced and combines > two operations - changing state and navigating - in one command. My sense is > that this is more confusing than helpful to most users. Steffen, if it is only your sense, why did you closed this bug? As you've seen, I've cc'ed Mik as he always wants to have his foot on all UI issues, so I'd appreciate if you would wait Mik to comment on this. > I would prefer to put effort towards fixing bug 208923 which was the motivation to > have this advanced command instead of overloading the UI. That is sound strange to me. How is this issue prevents you from working bug 208923 ? > Yes, that's why I support having advanced actions in Mylyn but that doesn't mean > the UI needs to expose all advanced functionality in prominent places. I still don't see why do you call this advanced action. It is very naturaly helps with reviewing incoming tasks workflow and in some sense it is practically the same interaction as "Replace/Find" action in standard search dialog. > Please note that go to "Next Unread Task" action is discoverable through the > Navigate menu. Navigate / Goto menu is probably the really last place I would look for those actions. It took me quite wile to find it even after you mentioned Navigate menu and those actions look really strange next to disabled standard Next/Previous actions in the same Navigate menu.
Apparently we are not converging. I have stated my opinion and recommend to not add additional UI to make this advanced command discoverable. In my opinion the current solution which lists the command in the "Keys" preferences page is sufficient. Reassigning to Mik.
I agree with Steffen's points and decision to keep this out of the current UI. Eugene: can you provide an example of a mail reader that provides this as a separate action and not a default action, including how they structure the menu and/or shortcut? Steffen: as you already know this action is quite useful. I think that the best chance that we have of exposing its utility is to make it a default action (e.g. after you have read an incoming, you automatically jump to the next, e.g. when in focused more or an incoming presentation). For 3.0 let's make sure to review your additional navigation actions and figure out how we can either incorporate more of them or teach them more easily.
(In reply to comment #7) > Eugene: can you provide an example of a mail reader that provides this as a > separate action and not a default action, including how they structure the menu > and/or shortcut? I said "an equivalent". As you know, most if not all email readers mark emails as read immediately or after short delay after selecting them in the list. After that "go to next unread" action will bring you to next unread email (in Thunderbird it is "N" shortcut). In a result, interaction is essentially is "mark as read and go to next". So your idea to make "mark as read and go to next unread" a default action would do exactly that. I like it.
FWIW, I'm one of the types of users who typically try to disable "auto mark read when viewed" because it is too common to browse and use unread as a marker to come back to it. Especially since mylyn doesnt have something like that (well, sort of, by scheduling it)... oh, and I'm not asking for it to have it. I just would rather be able to turn off behaviour whereby read is marked implicitly, if possible.
Eddie: thanks for the feedback. Also see bug 220006.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
