Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
5.2, 6.1-OD-08, 6.1, 6.1.7
-
5.02
-
10
-
Severity 3 - Minor
-
0
-
Description
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Description
If the name of a project is same as the key of another project, then, when using JQL to search by name on the first project would retrieve all issues from the second project.
First Symptom
Steps to reproduce
1. Create the first project with name: My Test Project, key: MTP
2. Create the second project with name MTP, key: MP
3. Seach with advance JQL:
project ="MTP"
4. All issues belong to My Test Project project are retrieved.
Expected result
All issues belong to MTP project should be retrieved.
Second Symptom
Steps to reproduce
- create first project with name My Test Project, key: MTP
- create second project with name MTP, key: MP
- create a new JQL, insert:
project=MTP
- select project with key MP from the suggested list
- hit Enter and the issue for project with key "MTP" is return
Expected Result
Issue for project with key "MP" is return as user manually select the project from the suggestion list
Workaround
Check a few workaround options at https://confluence.atlassian.com/jirakb/when-a-jira-project-key-is-equal-to-a-project-name-the-search-always-uses-the-key-1108089913.html
Attachments
Issue Links
- is caused by
-
JRASERVER-25872 Should not be able to set a Project Name to an existing project's name or key
- Closed
- is duplicated by
-
JRASERVER-35725 Advanced search using project name is impossible if the name used is equal to other project's key
- Closed
- relates to
-
JRACLOUD-35250 Wrong filter result if project name duplicate with other project key
- Closed
-
JRASERVER-23708 Road Map Gadget displays 'No Issues' for each version of a project even though there are issues for each of them
- Gathering Impact