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

Ability to remove an archived fix version from an issue

XMLWordPrintable

    • Icon: Suggestion 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.

      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.

            [JSWCLOUD-17116] Ability to remove an archived fix version from an issue

            Solomon O added a comment -

            Workaround

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

            Solomon O added a comment - Workaround Unarchive the  fix version , remove it from the issue, and then archive the  fix version  again.

            Anusha Rutnam added a comment -

            This functionality should exist but currently does not work due to the following bug: JSWCLOUD-23207 – Removing an Archived Version from a Jira issue repopulates it after page refresh..

            All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment - This functionality should exist but currently does not work due to the following bug: JSWCLOUD-23207 – Removing an Archived Version from a Jira issue repopulates it after page refresh. . All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Tammy Absheer added a comment - - edited

            At this time, archiving a Fixed Version does not completely remove the archived Fixed Version from the dropdown menu of a task when clicking into the Fixed Version field. Can you please update the Fixed Version archive function to hide the Fixed Version completely from the dropdown menu when it has been archived. This actually seems to be a bug to me, but based upon Roberto Amorim's email to me, the system is behaving as intended currently.

            R

            Tammy Absheer added a comment - - edited At this time, archiving a Fixed Version does not completely remove the archived Fixed Version from the dropdown menu of a task when clicking into the Fixed Version field. Can you please update the Fixed Version archive function to hide the Fixed Version completely from the dropdown menu when it has been archived. This actually seems to be a bug to me, but based upon Roberto Amorim's email to me, the system is behaving as intended currently. R

            Oleksii Hlushchenko added a comment -

            Please suggest at least a workaround, without admin permission

            Oleksii Hlushchenko added a comment - Please suggest at least a workaround, without admin permission

            Saghi Kungurov added a comment -

            please fix this.

            Saghi Kungurov added a comment - please fix this.

            Rob Berube added a comment -

            not a fan of this functionality. please fix.

            Rob Berube added a comment - not a fan of this functionality. please fix.

            Isa Muqattash added a comment -

            Please fix. Makes for a very awkward behavior when a ticket fails QA and goes back to Dev, then sits in the backlog while the release goes ahead. Eventually, the fix version is archived and the ticket is still in the backlog but still has the older fixed version, which throws off our queries.

            To manually exclude each fixed version is not a viable workaround. There are simply too many to exclude..

            Isa Muqattash added a comment - Please fix. Makes for a very awkward behavior when a ticket fails QA and goes back to Dev, then sits in the backlog while the release goes ahead. Eventually, the fix version is archived and the ticket is still in the backlog but still has the older fixed version, which throws off our queries. To manually exclude each fixed version is not a viable workaround. There are simply too many to exclude..

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

                Created:
                Updated:
                Resolved: