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

Archiving Old Issues



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

      21 December 2015

      Hi everyone,

      Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; however there are not currently any plans to implement this suggestion.

      When we've discussed archiving with our customers we've generally found that the number one reason customers want archiving is to improve instance performance. Customers usually also want to;

      • de-clutter
      • need to keep the archived records for traceability/audit compliance reasons
        However these two reasons are much lower priority secondary and tertiary needs.

      We knew that we could make a bigger impact on performance by working on JIRA's performance directly instead of delivering an archiving capability. Hence we focused our resources on that since June last year. This is why we were able to ship a significant performance improvement with JIRA6.4 and we've continued improving performance since.

      The effort required to make these performance improvements directly in JIRA are less costly than developing an archival solution. In addition the performance gains we've since delivered and have broader performance benefits for all users regardless of their issue/project count. We will continue to focus on improving performance as one of our highest priorities and therefore do not currently have plans to implement archiving.

      If you are experiencing performance issues you can also look at our scaling guide that gives some insight into all the factors that affect performance. i.e. you may also want to look at reducing instance complexity by doing things such as; reducing the number of custom fields, reducing the number of workflows, permission schemes and other JIRA configuration.

      Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Otto Ruettinger
      Principal Product Manager, JIRA
      oruettinger (at) atlassian (dot) com

      Original request description:

      We would like to have the ability to archive old issues. We currently have an installation of JIRA (3.0.3) that has grown to 50,000 + issues. Out of these, about 35k are closed issues. We would like to be able to remove these issues from the database so that our installation has a smaller amount of issues. As an example, all issues that are more than 90 days old would be removed from the database, but they would still be useful for a Knowledge Base.

      To summarise, a feature that would remove or export issues (with comments) of certain age would be very useful.


        Issue Links



              Unassigned Unassigned
              4f86d9b1e4f1 David Alonzo
              356 Vote for this issue
              259 Start watching this issue