Defect #1013
Custom queries can be saved under same name
| Status: | Confirmed | Start date: | 2008-04-08 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Issues | |||
| Target version: | Candidate for next minor release | |||
| Resolution: | Affected version: | 2.2.1 |
Description
I think that query name should be unique.
We probably want to allow same name of queries for different users (so user A can have private query with same name as user B), like "My issues".
For uniqueness we shoudl check:
- In all queries of one users, including global public queries
- Global public queries
Related issues
History
#1
Updated by Thomas Lecavelier almost 15 years ago
- should be a feature request (damn, that's the day!)
- I agree with your point.
#2
Updated by Rocco Stanzione almost 15 years ago
Please test my patch from #1021
#3
Updated by Mischa The Evil over 13 years ago
Added relation to issue #3180.
#4
Updated by Daniel Felix about 10 years ago
- File DuplicateReports.png added
- Status changed from New to Confirmed
- Target version set to Candidate for next minor release
- Affected version (unused) set to 2.2.1
- Affected version set to 2.2.1
This defect is still included in Redmine 2.2.1.
I just verified it.
It should be corrected to the next minor release, as it's very misleading to have reports with the same name.
This could be tricky.
Example:
UserA with ReportA save this report in his personal reports.
UserB adds ReportA (other definition) as a global report. Those doesn't differ from all the other Reports. There must be some type of category to differ those reports and render them in two seperate groups in the sidebar. Or just add some symbol for them (personal and global).
This bug is bigger than expected. The delete of one of the two created reports delete both. It seems that the report is searched by it's name. This could explain why both reports will be dropped!