Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-77880

Renaming a version breaks all related filters

XMLWordPrintable

    • 3

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Filters that search based on a Fix Version or Affects Version break after the related version is renamed. 

      Steps to reproduce:

      1. Create a filter that searches for a matching Fix Version which is assigned to at least one issue
      2. Using that filter returns the resulting matching issues as expected
      3. Rename the Fix Version on that project
      4. The filter will no longer return any results

            [JRACLOUD-77880] Renaming a version breaks all related filters

            Guy Anela added a comment -

            +1 

            Until this is addressed, a workaround is to use the Release ID instead of the Release Name in your Filter JQL (e.g. Use fixVersion=1234 instead of fixVersion="Release ABC"). That way if the Release Name changes, the Filter will continue to work. You can get the ID by navigating to Releases and clicking on the specific Release; You should see the ID in the URL...

            https://yoursite.atlassian.net/projects/ProjectKey/versions/1234/tab/release-report-all-issues

            I hope this helps. Cheers!

             

            Guy Anela added a comment - +1  Until this is addressed, a workaround is to use the Release ID instead of the Release Name in your Filter JQL (e.g. Use fixVersion=1234 instead of fixVersion="Release ABC" ). That way if the Release Name changes, the Filter will continue to work. You can get the ID by navigating to Releases and clicking on the specific Release; You should see the ID in the URL... https://yoursite.atlassian.net/projects/ProjectKey/versions/ 1234 / tab/release-report-all-issues I hope this helps. Cheers!  

            kclark added a comment - - edited

            With the recent move of some Jira fields to GUIDs (assignee/reporter, teams, etc.), I am hoping versions will shortly follow suit. We regularly base filters on versions to organize our work on upcoming releases. Having to update every filter & dashboard to accommodate name changes to a release causes frustration and lack of trust in the voracity of our reporting.

            kclark added a comment - - edited With the recent move of some Jira fields to GUIDs (assignee/reporter, teams, etc.), I am hoping versions will shortly follow suit. We regularly base filters on versions to organize our work on upcoming releases. Having to update every filter & dashboard to accommodate name changes to a release causes frustration and lack of trust in the voracity of our reporting.

              83a31c241e41 Franziska Schindler
              eda4bad1cc88 Felipe Gaiotto
              Votes:
              8 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: