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

Ability to archive (deprecate) issue types (Issue Type Scheme) while keeping them on existing issues

XMLWordPrintable

    • 24
    • 14

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

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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
            Votes:
            134 Vote for this issue
            Watchers:
            62 Start watching this issue

              Created:
              Updated:

                Estimated:
                Original Estimate - 40h
                40h
                Remaining:
                Remaining Estimate - 40h
                40h
                Logged:
                Time Spent - Not Specified
                Not Specified