JIRA Issue Archival Procedure

Question

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

Nic Brough -Adaptavist- · Answer

>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.

eClerx Orion · Answer

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

Nic Brough -Adaptavist- · Answer

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.