-
Suggestion
-
Resolution: Unresolved
-
4
-
35
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Assuming the following:
- I have a project named PROJECT with key PROJ
- I create a filter:
project = PROJECT
- If I rename PROJECT to NEWPROJECT then the field produces
Suggestion:
Is it possible to bind the search to the project key or issue type ID instead? That way, renaming a project should leave filters unaffected.
Workaround
Edit the filters to update the project or issue type names
OR
Just noting here that you can save a filter that refers to a project by its ID rather than its name. If you do this, the saved filter will not be broken if you change the project's name.
To find all your projects' IDs, go to https://<your site name>.atlassian.net/rest/api/3/project/search
In the following example the id of my project is 10084:
To use it in a filter's JQL you need to type project = 10084
After changing the project's name, the saved filter referring to the project's ID continues to work:
Whereas the saved filter that referred to the project name has broken:
- is duplicated by
-
JRACLOUD-38436 Changing project name doesn't reflect in Advance filter query
- Gathering Interest
- is related to
-
JRACLOUD-76466 Jira should store the custom field details based on field ID instead of the field name
- Closed
-
JRACLOUD-79983 [Tracking in issue links] Various issues related to actions that cause broken Saved Filters
- Gathering Interest
-
JRASERVER-30467 Renaming a project or issuetype breaks filters saved with the old project or issue type name
- Gathering Interest