Hi Team,
We are planning to Archive the issues available on our server and would like to know the best approach for it.
Any suggestions you can provide please.
Thanks and Regards,
Tanishka S Chotwani
Hi Tanishka,
There is a knowledge base article titled Archiving a project that you may want to review. In addition, here are some posts with some suggestions the Community has used:
Solved: Is it possible to archive a Jira issue (not delete it)?
In addition, there was a Feature Request and there is an add-on called Exalate that was suggested in one of the comments that you may want to take a look at as well.
Cheers,
Branden
Hi Branden,
That information is not much helpful. I have heard of some utility that is provided by atlassian for JIRA ISSUE ARCHIVAL.
Can you please help out with that or any details on it?
Thanks a Lot.
Regards,
Tanishka S Chotwani
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You'll need to tell us what you heard of to get any further with it - The documents Branden pointed you to cover the Atlassian options, and most of the approaches using non-Atlassian stuff.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nic,
The idea we have is to archive old issues from PROD server so that the load from the server is reduced for better performance on server.
Also, the archived issues should be accessible to users at any time if they need with the same ID's and data.
When we try to archive issues by moving them to other project, the key gets changed so that does not look helpful.
Any suggestions please.
Thanks and Regards,
Tanishka S Chotwani
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>Also, the archived issues should be accessible to users at any time if they need with the same ID's and data.
That completely obviates the point of an archive. Your best option is to simply put them in a state where they can't be updated.
If you want to move them out to another server, then you'll need to find or write something that can scrape out issues and duplicate them in an "archive" JIRA. This is something Atlassian looked at when they first started to work on Data Centre, but abandoned as it was looking like a bigger task than Data Centre itself.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.