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

Archive project components


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

      Atlassian Update – 25 October 2018

      Hi everyone,

      Thank you for your votes and thoughts on this issue.

      We fully understand that many of you are dependent on this functionality.

      After careful consideration, we've decided to prioritize archiving components on Jira Server roadmap. We hope to start development after our current projects are completed.

      Expect to hear an update on our progress within the next 6 months.

      To learn more on how you suggestions are reviewed, see our updated workflow for server feature suggestions.

      Kind regards,

      Jira Server Product Management

      Original request description

      I use the project components very heavily for issue list filtering and rely on them for building out lists in Confluence using the



      In order to preserve those lists, I have to keep the component around, unfortunately, many times I don't necessarily need it for future work. So I don't want to present the developers with the component if it doesn't really apply to work anymore.

      It would be great if there was a mechanism to "archive" components just like you would with a release version, such that the user can no longer select that component for issues.

            izinoviev Ilya Zinoviev (Inactive)
            f983a72c130d Aaron Godert
            591 Vote for this issue
            350 Start watching this issue