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

            [JRASERVER-16683] Ability to archive (deprecate) issue types (Issue Type Scheme)

            And me also. This would be very useful for the reasons people have given above.

            Lindsay Peters added a comment - And me also. This would be very useful for the reasons people have given above.

            Please add me to the list of customers requesting this feature.

            John Mabunga added a comment - Please add me to the list of customers requesting this feature.

            Waiting on it too

            Debora Habeck added a comment - Waiting on it too

            The option of retiring an Issue Type would be great. Is there an update for this request?

            Gregory Kremer added a comment - The option of retiring an Issue Type would be great. Is there an update for this request?

            Priceless, instead of using validators and behaviors

            Yulia Ploshevsky added a comment - Priceless, instead of using validators and behaviors

            Adding an option to hide issue types seems like a relatively easy implementation and would provide me (and others) a great deal of value.  

            We have many issue types.  As I understand it, that was the only way to control what screens showed up.  Now, I don't need old issue types for deprecated functionality to still show up in that dropdown.  However, we do want to maintain those issue types on the existing tickets for provenance.

            mike.daigle added a comment - Adding an option to hide issue types seems like a relatively easy implementation and would provide me (and others) a great deal of value.   We have many issue types.  As I understand it, that was the only way to control what screens showed up.  Now, I don't need old issue types for deprecated functionality to still show up in that dropdown.  However, we do want to maintain those issue types on the existing tickets for provenance.

            Atlassian Update –

            30 November 2020
            Hi everyone,

            Thanks for your interest in this issue. This suggestion is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

            For the nearest future we've decided to prioritize other areas of the Jira Server and DC roadmap, including other options for keeping your Jira clean.

            We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.

            Kind regards,
            Jira Server Product Management

            Jakub Kurcek (Inactive) added a comment - Atlassian Update – 30 November 2020 Hi everyone, Thanks for your interest in this issue. This suggestion is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. For the nearest future we've decided to prioritize other areas of the Jira Server and DC roadmap, including other options for keeping your Jira clean. We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here . Kind regards, Jira Server Product Management

            Hi,

            Do you have any update on this?

            Thanks in advance.

             

            Humberto Gomes added a comment - Hi, Do you have any update on this? Thanks in advance.  

            Is there any update on this?

            Shantharam Nekkar added a comment - Is there any update on this?

            This is a real need. I can only echo what is said above. We need this solution. Having a growing list of unused issue types in our drop-down is not good for anyone. Removing the issues removes or changes historical data. This would go up against retention policies, and for some, a possible violation of the Federal Records Act. We need the ability to change our custom issues without compromising what has gone before.

            Michael Golla added a comment - This is a real need. I can only echo what is said above. We need this solution. Having a growing list of unused issue types in our drop-down is not good for anyone. Removing the issues removes or changes historical data. This would go up against retention policies, and for some, a possible violation of the Federal Records Act. We need the ability to change our custom issues without compromising what has gone before.

              Unassigned Unassigned
              brycenesbitt Bryce Jira Nesbitt
              Votes:
              180 Vote for this issue
              Watchers:
              88 Start watching this issue

                Created:
                Updated:

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