Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-16683

Ability to archive (deprecate) issue types (Issue Type Scheme)


    • 14
    • 6
    • 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.

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

      So I've got a long list of components and issue types, e.g:

      • New feature
      • Improvement
      • Task
      • New Employee Setup
      • Specification
      • Customer Initiative
      • Blah
      • Blum
      • Boo

      In https://jira.bepress.com/secure/project/DeleteComponent!default.jspa?cid=XXXX ,
      If these issue types or components are in use, Jira makes me reassign them before deleting them.

      Instead I'd like to deprecate them, so they can't be assigned to new tickets, but history is not changed.

      My goal is to reduce clutter, when issue types are no longer relevant for new tickets.

      The same comment applies to several areas in the administrative GUI. I want to "ghost out" old stuff, without changing history.

            Unassigned Unassigned
            brycenesbitt Bryce Jira Nesbitt
            174 Vote for this issue
            89 Start watching this issue


                Original Estimate - 40h
                Remaining Estimate - 40h
                Time Spent - Not Specified
                Not Specified