| Re: [mylar-dev] repositories for web-linked tasks |
Mik Kersten wrote:
I would probably be ok with that if new task and new query dialogs would allow to add repository in place:I don't think it's that bad for the user to have to create a new repository, as long as they only have to do this once per repository. 155153: Add Task Repository action should be on all repository selection wizard pages https://bugs.eclipse.org/bugs/show_bug.cgi?id=155153 The idea is to add queries to the same list where repositories are shown now (first page of add query, add new and existing tasks).I'm not sure I follow your second point, could you elaborate? This will give additional benefits. For instance, user can use data from query to fill in fields in the new issue (same way as it is done now for implicitly from the selection in Task List). Interesting. You are suggesting some sort of templates here. Good idea, don't forget to do some escaping.The main thing that I think is currently painful is that the user has to enter the identifiers for their project 5 or more times before they're done with their first query, which is error prone. I wonder if you could make "project identifier" a setting on the repository settings page. E.g. for "Subclipse (IssueZilla)" it would be "subclipse.tigris.org" and for "Azureus (SourceForge) it would be "atid=575154&group_id=84122". Once entered on the repository settings page you simply refresh all of the fields that depend on it. Then, when the user specifies that they want to create a query for that repository you use this to automatically populate the URL and Regexp, removing the step of them having to re-select the template Generally it should allow to ignore that repository id and use hardcoded values if repository id can't be extracted. 155160: Simplify query configuration for web repository https://bugs.eclipse.org/bugs/show_bug.cgi?id=155160 It is only confusing because there are dummy repositories. Currently you can actually create query pointing to any web repository, so it is just a confusion. The repository is only needed for adding new and existing tasks.(confusing, since it makes no sense to select an 'incompatible' template). regards, Eugene -----Original Message----- From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx] On Behalf Of Eugene Kuleshov Sent: Thursday, August 24, 2006 2:04 PM To: Mylar developer discussions Subject: [mylar-dev] repositories for web-linked tasks Mik, I just realized that we do need repository to create web-linked tasks. So, we have two options to resolve this issue: -- either leave this as is, and require user to create new repository. -- add existing queries to the list that is currently show repositories, so you can go either with repository or query... What do you think? regards, Eugene _______________________________________________ mylar-dev mailing list mylar-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/mylar-dev_______________________________________________ mylar-dev mailing list mylar-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/mylar-dev |