Archived projects question

[Mike Leydet]

Background: Currently on Jira Software Cloud Standard

We create a project for each client and use multiple types of issue types in each project. Each project is essentially the same structure. When a client churns, we change the project lead to a dummy user, and append the project title with "zz" so it moves to the end of our projects list. All issues are moved from whatever status to either Done or Abandoned. (hacky way to archive projects)

This causes our backups to get quite large. Archiving seems like a good option, but the cost for Premium is a bit more than we would want to spend if it doesn't actually solve our problems. 

If we upgrade to premium and archive 50+ projects, will that:

1. Enable us to reduce the size of our backups? We backup and restore our Jira instance to a staging instance to test our home brew apps that interact with Jira, it currently takes a long time to do this. 

2. Can we still access the archived issues via API? We have a tool that searches issues via API and displays pertinent information, so we want to be able to access relevant info, even if archived. 

3. Is there a way to automate our mirroring process of backing up and restoring to our staging Jira instance? 

[Anand Sanke]

@Mike Leydet 

1. Enable us to reduce the size of our backups? We backup and restore our Jira instance to a staging instance to test our home brew apps that interact with Jira, it currently takes a long time to do this. 

If we archive projects, it means projects will be removed from jira indexing but not from database. So your database backup size will be remain same even after archiving projects. What we will get is "fast search as performance improvement", full indexing time will be reduced, index file size will be reduced.

2. Can we still access the archived issues via API? We have a tool that searches issues via API and displays pertinent information, so we want to be able to access relevant info, even if archived. 

I did not verified but red some where as it is possible with REST APIs

3. Is there a way to automate our mirroring process of backing up and restoring to our staging Jira instance? 

Yes we can automate it to some extent based on program language we select. We will have database commands to take backup and restore. We can stop and start jira service using windows batch commands (if jira is on windows server). We can remove application links, change base url using jira REST API calls. With one or multiple scripts we can automate most of the jira mirroring process.

[Mike Leydet]

@jirasupport Seems like a relatively easy question for you.