-
Suggestion
-
Resolution: Unresolved
-
8
-
Steps to reproduce
- Create a project with the project key "ABC" with any name.
- Rename the project key to "DEF"
- Create another project with any key and the project name "ABC"
- Create issues in the project named "ABC"
- Attempt to search for issues in the project named "ABC: using the following JQL:
project = "ABC"
Expected results
Return issues from the ABC projects
Actual results
No issues returned.
Original description
Hi,
We have a Agile board (configured for project ABC, & filter is configured using JQL query like below):
project = "ABC" ORDER BY Rank ASC
Now, say project ABC has been renamed to XYZ, then you can't see any issues under Agile board since board still uses filter JQL query which points to old project with name ABC.
Solution looking: So actually if project is renaming from ABC to XYZ then it should reflect at each and every place including JQL filer query. I think this is an issue with jira & needs to be rectify.
Jira System should able to update name at each & every place in system, as its not possible for user to go & check/change in each and every board that used old project name.
JIRA Agile (v6.3.13.1)
Reference: JSP-193610
Regards,
- Vishal
- duplicates
-
JRACLOUD-30467 Renaming a project or issuetype breaks filters saved with the old project or issue type name
- Gathering Interest
- is duplicated by
-
JRACLOUD-82292 Unable to search issues with Project name once the project key is renamed
- Closed
- is related to
-
JRACLOUD-37353 Agile Board Filters Should Use Project Key
- Closed
-
JRACLOUD-37487 JIRA should warn users of possible impacts caused by filter updates
- Closed
-
JRASERVER-38436 Chaging project name doesn't reflect in Advance filter query
- Closed
-
JRACLOUD-79983 [Tracking in issue links] Various issues related to actions that cause broken Saved Filters
- Gathering Interest
- relates to
-
JRACLOUD-2703 As an Admin, I want the ability to edit a project's key
- Closed