You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Ok, I did need a clickbait title to get your attention but trust me, it will be worth it.
Archiving issues in Jira really helps improve overall performance (think about all those JQLs that are returning 1000's of issues on your search, your roadmaps, your boards, etc).
Native archiving features were released over 18 months ago, I believe in version 8.6. Yet, I don't see many of my peers in the industry maximising it. I would love to understand why? What are the limitations? Any other considerations?
Or if you have tried it, did it help? Would you recommend it to your peers?
I would love to hear more from the community. Please comment and share your thoughts.
And before I go, to stay true to my title, you will find the 3 simple steps below.
1. Archive old/unused projects (https://confluence.atlassian.com/adminjiraserver/archiving-a-project-938847621.html)
2. Archive issues older than 12 months (https://confluence.atlassian.com/adminjiraserver/archiving-an-issue-968669980.html)
3. Or, quite simply do it all in one step using the API (https://confluence.atlassian.com/jirakb/is-there-an-easy-way-to-archive-a-lot-of-issues-976766896.html)