| Summary: | allow to create multiple queries with the same name | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Sam Davis <sam.davis> | ||||
| Component: | Mylyn | Assignee: | Sam Davis <sam.davis> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | steffen.pingel | ||||
| Version: | unspecified | Keywords: | contributed | ||||
| Target Milestone: | 3.6 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Sam Davis
While this may be technically possible I am hesitant to support multiple queries with the same name as it could lead to confusion. For the sake of consistency the rename action would need to be fixed to not allow that. I'll bring it up on the Mylyn call for discussion. I could see disallowing queries with the same name and same repository, but I don't really see why it would be confusing if they are for different repositories, since the repository name is shown on the query. It just forces people to use query names like "My Bugs 2" which isn't very illuminating. BTW, currently multiple repositories with the same name are allowed, which seems worse to me, and multiple (local) tasks with the same name are allowed as well, which seems by far the most likely to cause confusion, but should probably be allowed anyway. +1 Otherwise we force people into awkward naming patterns. Note this means that we should always default to showing the repository label as part of the query label. +1 Sam, let me know if you are interested in providing a patch. Created attachment 192787 [details]
patch
This will allow queries to have the same name, but will not allow queries and categories to have the same name. It will also prevent repositories from having the same name, which means that anyone who already has 2 repositories with the same name will have to rename one before they can modify its properties.
Thanks Sam! I have applied the patch with minor modifications. I tweaked the Bugzilla page slightly since it was never showing the message and I also changed the logic slightly to only show the warning if a duplicate query is created in the same repository. (In reply to comment #7) > only show the warning if a duplicate query is created in > the same repository. I wonder if this should actually be an error? I think it's sufficient to show a warning for now. As you pointed out there are multiple ways to set the name on a query (e.g. rename, import) and unless we fix all of these cases I don't think it's worth preventing this in the query dialog. |