Backup before Switching Schemes

Question

Hi,

I'd like to "switch schemes" for a project.  The process looks pretty straight forward, but the project contains many issues, and I don't want to risk messing up the status of those issues.  Can I copy the project or take some kind of backup before I attempt this?  Thank you.

Andy

Andrew Saxsma · Answer

Hearing no more discussion on this topic, in case anyone is trolling this for product improvements, I'll close with a suggestion to add some convenient "undo" button for these operations.  Thanks everybody!

Andrew Saxsma · Answer

Thanks for the reply Nic.  I am changing workflows.  The project has 227 issues, it would be a COMPLETE DISASTER if I the status fields of all the issues got messed up.  I am worried about a scenario, for example, where either by the fault of operator error or of Jira or some cosmic event (who knows), they all end up with the DONE status.  I need some kind of "undo button".

Is the Settings->System->Backup manager an option?  I see two options: Back up for cloud and Back up for server.  I believe I am on the cloud.  For the Cloud, I pressed the "Create backup for cloud" button and it seems to have generated a backup file that I was able to download of all the projects for my installation.  However, for the Settings->System->Restore system, there doesn't seem to be a way to restore only one project.  There may be more options beyond the "Begin import" button, but I'm afraid to press it in case it actually starts restoring the whole database for my installation.

I also understand after reading some of entries in the community page that Atlassian performs backups and can restore a project.  What recourse is available here?

As a last resort, a CSV download of all the issues could be made, and worst case, restore the status by hand.

Nic Brough -Adaptavist- · Answer

The only thing that might mess up the status is if you change the workflow scheme.

The issue status will only be affected if the new workflow for any given issue does not contain the same status the issue is already in.

Imagine you have a simple case of two workflow schemes.

* Scheme 1 has one workflow with "Open -> In Progress -> Testing -> Done"
* Scheme 2 has one workflow with "Open -> In Progress -> Done"

When you swap schemes on the project, any issue that is currently in "Testing" will have to be moved to one of the others.  Jira will explicitly ask you how to map status when this happens, and let you cancel the migration.

Something similar (but a bit more simple) happens for Priority schemes too.

As for the other schemes - you can put them back very easily without actually touching your issue data at all!  They're all about how it all works, not the actual data!