Two JIRA instances, Production and Archive

Marc Jason Mutuc

Since our Production instance is getting big, we would like to move old tickets to an Archive instance and implement a retention policy on Production.

Starting it should fairly be easy but, having to move tickets from Production to Archive on a weekly/monthly basis poses a challenge.

Goal here is to keep everything: comments, attachments, etc.

Initially, a restored on the Archived using the back-up of Production then doing some spring cleaning on both instances would be manageable. 

But, how do we go forward when we need to move (or bulk move) selected tickets from Production to Archive? Thereby keeping Production with a low number of tickets and just dumping old tickets on Archive every week/month.

Maybe someone has done this before.

Joe Pitt

The Archive function is only available on the data center version of JIRA.

You can create another project with limited permissions to store old issues in and move them there. They will get a id but can still be searched for under the old id. All the comments and attachment will move to the new project. 

If you want to create a new instance of JIRA and store old issues there you will need a plugin for that. I think the name is Project Manager. That means another license for JIRA and the plugin will also need a license.