Community
Participate
Working Groups
Build Identifier: Eclipse: 20090920-1017, Mylyn: 3.3.0.v20091015-0500-e3x One query should be devidable in at least three sub groups. Group 1 should contain all matched tickets, that are new. Group 2 should contain all matched tickets, that are resolved. Group 3 should contain all matched tickets with state closed. Using three separate queries would be possible, but would waste a lot of room. Reproducible: Always
If I understand correctly you are suggesting to add an option to sort tasks by completion state. To help us prioritize the request could you provide more details about your use case? How and when would you use this sorting mode?
Well, sorting the tickets by completion state would be the simple way. But not a nice looking and convenient presentation. I actually suggest sub groups. So you would create a new query and include all the tickets, that are owned by you. In the Task List there would appear two new groups: The one for your query and one for tickets not matched by your query. The unmatched groups will always be at the bottom and will not even be grouped with the query. I would like these two groups/lists to be subgroups of the main query group with the second one to be hidable. Additionally the matched tickets should be devided in three parts as described in my additional comment. So a query would display as follows: ## Other Query title ## ## My Query title ## +-> ## New Tickets ## +-> ## Resolved (but open) Tickets ## +-> ## Closed Tickets ## +-> ## Unmatched ## ## Yet another Query title ## Hence the new title for this bug is not as good as my original one, because I am not suggesting this sort possibility. The use case should be pretty clear. When someone creates a new ticket for one of my projects, it is "new" and assigned to me (1st sub group as above). Then after I fixed the bug, I set the state to "resolved" and resolution to something like "fixed". The state is not "closed". The current Mylyn would still show the unclosed ticket in the list of my open tickets and wouldn't show any visible difference to the other tickets, which might be new. Hence I don't see, how much and what I still have to do and what I have already done. In my suggestion this ticket would be removed from sub group 1 and moved to sub group 2. When the reporter accepts my fix, he sets the state to "closed" and the ticket would be moved to sub group 3. This way I can very clearly see, what's up and what to do, etc.
Thanks for the detailed information and great use case description. I can see how this would be a useful addition. The UI Experiments feature in the sandbox has support for different presentations and it would probably be feasible to add a presentation for workflow states as you suggest. It could be a bit tricky to come up with a schema that works across repositories though since workflow states vary between repositories. I have marked the bug has as helpwanted to indicate that we would be happy to support a community contribution to resolve it.
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
