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
What are the best ways to archive projects and issues in jira server.
Considering archiving option is not available in jira server. what are the best ways to archive data and is it possible to make automation for this process.
We would like to keep the data outside of jira server. b/c archieving too much data which will still be loaded for index, search for admins etc and this might affect the performance.
we would like to archive issues that are closed for more than 1 year.
How we can do the same for confluence server.
To archive pages on Confluence Server, Data Center and Cloud, there is a dedicated popular app available: Better Content Archiving for Confluence.
Note that it supports the "archive after one year" lifecycle rule and provides auto-archiving capabilities (automations) that you requested:
The question is, what do you want to achieve?
You can make backups and remove the projects from your production server, there will be a lengthy process to restore them.
You can make csv exports and remove the projects, so you can still browse the issues, but are not able to restore everything in Jira.
You can make a permission scheme which will not allow anybody to see the 'archived' projects, so you can restore them quickly. Disadvantage, the issues are still being indexed, so indexing is slower.
The only thing I can think of if that you use 'Issue security' and Automation for Jira.
Now users will not see issues where the security level has been set. They can only see it when they are in the role Archive viewer.
Note, this will only hide issues from most users, but they still exist in the project and are still indexed by Jira. But they will not be seen in reports, dashboards etc (if you not have the aforementioned role).