Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-30467

Renaming a project or issuetype breaks filters saved with the old project or issue type name

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 5
    • 8
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Assuming the following:

      1. I have a project named PROJECT with key PROJ
      2. I create a filter:
        project = PROJECT
        
      3. 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

      1. Look for all filters using the old project name in the database
        select * from searchrequest where reqcontent like '%PROJECT%';
      2. Edit the filters to update the project or issue type names

        1. error.png
          20 kB
          Theodore Tzidamis

            Unassigned Unassigned
            ttzidamis Theodore Tzidamis (Inactive)
            Votes:
            81 Vote for this issue
            Watchers:
            58 Start watching this issue

              Created:
              Updated: