Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-17116

Ability to remove an archived fix version from an issue

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Tracked Elsewhere
    • None
    • 1
    • 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.

    Description

      It is not possible to remove a fix version from an issue once that fix version is archived (this is still true in JIRA v7.5.3).

      Already in 2005 this behaviour was reported as a bug, see {}JRASERVER-6419{}, but it was resolved as "works as designed".

      Now in 2017 people still do not understand why it was 'designed' this way, again see the comments on {}JRASERVER-6419{}. Hence this feature request.

       

      Workaround

      Unarchive the fix version, remove it from the issue, and then archive the fix version again.

      Attachments

        Issue Links

          is cloned from

          Suggestion - JRASERVER-66492 Ability to remove an archived fix version from an issue

          • Gathering Interest
          is superseded by

          Bug - A problem which impairs or prevents the functions of the product. JSWCLOUD-23207 Removing an Archived Version from a Jira issue repopulates it after page refresh.

          • Medium - Medium priority issues
          • Long Term Backlog
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-6419 Unable to remove archived version from issues

          • Low - Low priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              033163b8b1fa Gerrie Kimpen
              Votes:
              36 Vote for this issue
              Watchers:
              27 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: