Community
Participate
Working Groups
I would really like to have Mylar close the current active Task as fixed as soon as I comitt the changes for this bug. I would also like to define a comment template, ideally "Fixed > Date", where date is replaced with the current date. As an alternative, a contextual menu entry "Mark as Fixed" would be handy for the Task View too. Ben
These workflow enhancements could be a good Google Summer of Code project: http://wiki.eclipse.org/index.php/Mylar_GSoC_2007 We have some of them on our 2.0 plan, but won't be able to get to all of the itneresting workflow combinations.
I agree with adding "mark as fixed" to the context menu for the Task List and task Search results. Other good items to be added the context menu include options to set the priority, target milestone, and severity, and the ability to assign bugs to yourself. These would be really powerful, as I have several times wanted to quickly make changes to multiple bugs, and supporting multi select in the Task List, coupled with these new menu items, would result in even more productivity.
I don't think menu items like you describing are going to work (not all connectors have priorities, milestones and severities and meaning of assigning issues is different between connectors). It seems like we'll need to add some connector-specific support for group operations that may need special UI.
It's doable though, right? For instance, in the explorer view, you get a different set of context menu items contributed depending on whether a Java file, XML file, or folder is selected. Why couldn't a different set of items be added depending on whether the selected task is a bugzilla task, personal task, or other connector task? Maybe the Task List isn't yet designed to allow for dynamic menu contributions?
Yes, the Task List does support dynamic menu contributions ("Schedule" and "Move to" are both dynamic). The challenge is that from the point of view of the Tasks API this is a request to allow in-place editing of repository task attributes. This is a bit tricky because we would need to figure out which attributes should be editable in this way to avoid blowing up the context menu. Additional trickiness comes and because some attributes require additional input. For example, marking a Bugzilla bug resolved requires a comment to be specified. So there is a bit of a slippery slope here since integrating fancy editing functionality into context menus may require wizard-style dialog interaction and we are trying to avoid modal wizards. What would be great is if the people wanting this functionality could outline each use case they are interested in, including the flow through the UI. Then we can figure out how to streamline in-place editing and performing operations on multiple tasks at once.
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
