Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

What should be the best practice for addressing/removing very old issues in Jira?


We follow a practice of archiving projects not used for 6 months. Then keep the these projects archived for another considerable duration and finally remove them permanently after taking a longterm backup. This practice has been helpful for us to keep list of our projects in Jira checked.

But we have a huge list of active but very old projects also which have been growing. 

My question is that how do we handle such projects which are growing and have a huge amount old issues. So for example we have around few hundered thousands issues which were last updated 2 years ago. I simply want to remove them. But it seems easy saying than done.

One thought is that take all the closed, resolved, rejected, duplicate etc. issues and address them first. 

whenever I take this up with agile coaches, they get jittery about it. and ask me questions like, how can we restore the issues? will they be restored with same contents, description, history, comments etc? what if they have links and included in the sprints etc. 

well ofcourse I can produce these scenarios and find the answers. 

but what does the community suggest about this situation? is there any best practice that can be adopted?



2 answers

0 votes
Andrew Laden
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 27, 2023

The DataCenter editions of jira (which you will have to start using in less then a year if you want support anyway) have a feature for Project Archiving.

One option would be to create a "archive" version of the active project, with the same config etc. Move old tickets into that project, and then archive it.

Then every year or so, Unarchive it, move more tickets into it, and re-archive again.

That way nothing gets removed, links still work etc, but it gets out of your indexes and search results, which should improve performance.

There is also issue level archiving

Either of those should give you some options.

If you are looking for a more general "Best Practices" I think that is really organization dependent. I don't think there is a one-size-fits-all recommendation.

0 votes
Aron Gombas _Midori_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 25, 2023

We are developing the Better PDF Exporter app which is frequently used for archiving purposes.

It fits that use case simply because it captures all the details of an issue (field values, change history, worklogs, comments,  etc.). Even attachments can be embedded in the PDF document exported from an issue!


So customers export their issues to PDF, put those to a doc management system (for searching purposes) or just a shared drive on GDrive/Dropbox/Sharepoint, then remove the issues from Jira.

It doesn't support "restore", of course, but it is very easy to do.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events