The blog post (written by my colleague) titled How to archive Jira issues on Jira Server and Data Center compares multiple techniques.
If you haven't decided what to do yet, it is a great starting point.
Ok, that's fine, but it's not "archiving", it's "completely destroying the issues".
You can run filters for "issue last updated before 1st Jan 2017" and then run through bulk-delete for them, but that's only a thousand at a time. I'd script that from the outside, doing it over REST.
JIRA is not setup to archive issues. If you want to remove issues from your JIRA instance but archive them before doing so I would suggest coming up with a process internal to your organization that meets your needs. For example every quarter we do the following:
This provides us with the following:
We have yet to do a full restore to get the information we need. The PDF documents have been sufficient in answering questions that have come up after the project or issue has been deleted.
Hope this helps.
I'm currently considering how best to tackle this for one of my projects that has thousands of tickets also. Mostly because making jira changes take forever when the project is large.
What I'm throwing around in my head atm is cloning my current project and renaming it to include "Archive" in the name. Then I would query for all the issues I want to archive and use the Move function in Jira to shovel them over into that other project. I'm thinking this might be the best way for them to be queryable, but out of the active project.
As for 'read only', there are a few ways you could probably do it: project-level edit permissions, or you might create a custom workflow with no statuses except "Closed" and apply that to the new project (would prevent even admin-level users from changing the status of those tickets without them tweaking the project workflow).
Don't know if that's the best solution, but wanted to share my current thoughts on the topic.
Hi @hash ,
Wanted to share that we released issue-level archiving (archive individual issues, bulk edit through JQL search, or automated through APIs) in Jira Software Data Center 8.1, and a new browse archives page in 8.4. Here's our announcement and blog with all the details:
We do not have plans to release issue archiving for Jira Software Server, as this feature supports our enterprise value propositions for Data Center around high availability, performance at scale, and administrative control. If you'd like to learn more about how we prioritize features for each offering, this is a great resource: https://www.atlassian.com/blog/jira-software/prioritizing-features-server-data-center
Is it to clean up your Kanban? A quick fix for me was to create a quick filter instead of changing the status of items
Go to Kanban
Name the new filter
Enter into the JQL field - status != Done OR resolutiondate >= startOfWeek()
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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