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

Add ability to archive a custom field option

    XMLWordPrintable

Details

    • 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

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

      We are using JIRA to track production changes and need to keep an accurate audit trail of what has happened in the past. However, when a custom field option needs to be removed (no longer relevant for future issues), we can't have that field option being removed from past issues.

      Currently, if an option from a custom field is removed, JIRA removes that option for all existing issues that have it (closed as well). Same story with components - If I remove a component that isn't needed for future issues, it should not remove that component from previous issues.

      This is a lack of data integrity for JIRA. We should be able to modify field options for future issues without "breaking" the past issues.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              912467c9cc75 Tyler Tyler
              Votes:
              26 Vote for this issue
              Watchers:
              19 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: