Community
Participate
Working Groups
Would be handy to add a new category to Task List populated from plain list of bug ids/keys (e.g. comma-separated "156123,128333,98012"). Right now I can achieve the same either with manually created category and adding bugs one by one, or to have a named query in a repository. Both are not that convenient.
I wonder what is the use case for this and which repository connector you need that for? By the way Mik, I noticed that "Add existing repository task..." action is not available trough Ctrl-N/Ctrl-Shift-N wizards.
It's just a convenient way to add few existing tasks at once instead of adding them one by one. It doesn't seem to be tied to any particular connector.
I just don't recall having a need in something like that while using Mylar for over a year now. So, curious where those task ids would come from? The closest use case is when you have query in the web browser and need to drag-n-drop links from that query to the task list...
Working in a team, there are different ways to communicate set of bugs you would like to draw attention to. It's not always handy to pass urls around, and plain lists of bug numbers are much more suitable. If a person gets "1,2,3,4" on IM and needs to go to repository and to create a query, switch back to Eclipse and to add a query to Task List -it's just odd, too many actions. If there's a need to add single bug (apparantly, there's a need, hence the action to add single task), some day there's a need to add few, and to accomplish that at once ;)
For our own usage and the usage we have noticed I have not seen users need to work with a collection of bugs that can not be represented as some kind of query, and we generally encourage using queries and discourage adding task explicitly. But if this is a use case that is important for others than we would be happy to take a patch that allows the dialog to accept a comma-delimited list, and adds each item in the list. Notes on contributing are here: http://wiki.eclipse.org/index.php/Mylar_Contributor_Reference
Well, first of all I don't see much difference between query based on substring in the summary field and query based on a list of bug ids. Both are queries to me, and hence "encouraged" way to proceed. Next, provided I can't create arbitrary query from Mylar (at least with Bugzilla - e.g. I can't specify keywords), I'm forced to switch to browser in addition to Eclipse/Mylar to overcome the limitation. Though I'm pretty sure the use case of adding few bugs by id is essential to any person overseeing complex project (let alone interacting with non-technical people addicted to using whatever medium to pass bugs around), I'm stuck trying to figure out what's the difference is between query in a form of "*GraphicalEditPolicy*" and "1,2,3"...
To create an arbitrary query in Mylar use the Web UI to create it, then do New -> Query -> Create from existing URL and paste in the URL. So now I'm curious, would you prefer to add multiple bugs by ID, or would you prefer to be able to create a query that's formulated by specifying IDs?
I do know about named queries; the drawback using them is that you need to go back and forth between browser and Eclipse, plus, they take additional "maintenance" efforts, e.g. deleting once no longer needed. Choosing between multiple bugs by id and extended query wizard I'd take former. Perhaps, it's just a matter of personal taste or a habbit overgrown to addiction ;), nevertheless, it seems to be much more simple to implement (let user enter more than single id in the existing dialog) and is connector-agnostic.
Artem, seriously, if you so desperate about this, why don't you contribute a patch? It would of taken you less time then convincing people who never saw need in this feature. :-)
It sounds like we have converged on the approach and I updated the summary accordingly. Eugene: we can't expect all users who are willing to provide feedback and discussion on how they want the tool to work to contribute patches, and when one user clearly outlines a use case, even if it is a corner one, it is worth discussing. Although as you point out for some cases like this it can actually take less time to contribute the patch and for us to apply it than to discuss it ;) Artem: we make it really easy to contribute and create patches, since the project committers tend to focus on streamlining and improving most common use cases. If you or anyone else is interested in providing a patch for this refer to the following on getting your workspace set up: http://wiki.eclipse.org/index.php/Mylar_Contributor_Reference
I wish I could insist on patches in our project (GMF) ;) Guys, I doubt the time I'd spend checking out the code, getting acquainted with the codebase, looking for particular class/method, adding tokenizer and for, finally creating a patch and eventually you reviewing/committing it is anyhow similar to that of yours fixing this right away. I'm not "desperate" about this functionality ;). It just seems nice idea to me; and the reason I spend time talking about it here is that I personaly don't like bug reports when committer can't get any feedback from the bug submitter.
It appears to be a simple enhancement. I would be happy to take a look at this after getting a solution to bug#165088, since it think perhaps it could deprecate the current "Add Existing Task" wizard.
(In reply to comment #12) > It appears to be a simple enhancement. I would be happy to take a look at this > after getting a solution to bug#165088, since it think perhaps it could > deprecate the current "Add Existing Task" wizard. That is another reason I didn't want to rush into this. :-)
Artem: we do not insist on patches. But we have limited resources and are largely a volunteer project, and ince there are so many use cases and workflows for working with tasks what many users have been doing is contributing workflows that make Mylar work better for them. To support those efforts we try to be very pro-active about supporting and applying patches. Willian: I'll put this in your queue for now in case it will be a quick fix after you are done with bug 165088.
Created attachment 56202 [details] Patch
Created attachment 56203 [details] mylar/context/zip
Can we also allow spaces as delimiters? Just in case...
Patch applied and verified, good stuff Willian. For now I changed the label text to: "Enter Key/ID (use comma for multiple)". Willian: could you please update the Users Guide with a note on this use case? http://wiki.eclipse.org/index.php/Mylar_User_Guide
(In reply to comment #18) > Willian: could you please update the Users Guide with a note on this use case? > http://wiki.eclipse.org/index.php/Mylar_User_Guide > I can do it, but actually there is no mention to this "Open Repository Task" on this guide. I can add a section if you want. Do you have a good screenshot?
Done. http://wiki.eclipse.org/index.php/Mylar_User_Guide#Open_Repository_Task_dialog
Yes, it would be good to add a screenshot because I have a feeling that many users don't know about this functionality.
