-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
5
-
8
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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
- Look for all filters using the old project name in the database
select * from searchrequest where reqcontent like '%PROJECT%';
- Edit the filters to update the project or issue type names
- is duplicated by
-
JRASERVER-66666 filters that had connection to bugs, were broken when Issue type renamed from Bug to Defect
- Closed
- relates to
-
JRACLOUD-30467 Renaming a project or issuetype breaks filters saved with the old project or issue type name
- Gathering Interest
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...