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)
👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events