Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-16184

Add ability to archive a custom field option

    XMLWordPrintable

    Details

    • Feedback Policy:
      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.

      Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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

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

                Dates

                Created:
                Updated:
                Resolved: