Before generating a dump file, upgrade the app (to version 8.2.2 or higher).
Restore of the App IS NOT restore of Jira
This feature does not guarantee that all Gantt, Scope, etc. data will remain the same as at the time that dump was done due to the difference of issue states present in the environment where the dump is restored and the synchronization process. After dump restore, the state shift and synchronization may result in irreversible changes to the Jira instance.
If you want to perform a full restore, you will need to create a backup of both:
Jira
the App
To successfully perform a restore of the state of both the App and Jira, you will need to:
At the same time, generate backup files for:
Jira
the app
To restore:
First, you need to stop the synchronization between the App and Jira
Restore Jira
Restore the App
Activate the synchronization between the App and Jira
Backup and restore of the App
Create a backup of the App
Go to BigPicture App configuration > Advanced > Database dumps.
Press the New dump button, add a description, and confirm the process by pressing the Create dump button.
The new database dump should appear at the top of the list of backups (a page refresh might be needed)
Restore the App backup on the same instance
Go to BigPicture App Configuration > Advanced > Database dumps
Press the Restore button in the line with the backup name.
Confirm the next step by selecting Restoring saved data and press the Next button.
Confirm the operation by entering the word RESTORE and press the Restore button.
Info: If the BigPicture instance is not new and some work has already been done on it, this work will be overwritten! BigPicture will automatically dump its current state before restoring it (so that the process can be reversed).
The database recovery process will start.
After the recovery process is complete, the restore is over. You can go to the BigPicture application and verify the correctness of the data.
Additional information - application version mismatch
If the dump was done on a newer version of the application than the one on which the restore is performed, such an operation will not be allowed to be performed. In this case, an application update to a newer version (on which the restore process is made) is required.
If the dump was done on an older version of the application and is incompatible with the newer version of the application, such operation will not be allowed to be performed. In this case, an application update to a more recent version (on which the database dump is made) is required.
Backup and restore of Jira
Create a Jira backup and download it
Cloud
Go to System > Backup Manager > Create backup for cloud
Server
Go to System > Backup system > Backup
Restore Jira backup on a staging environment
Cloud
Go to System > Restore System > Import data (import the Jira backup file)
Server
Go to System > Restore system > restore using the Jira backup file (Restore)
Stop/start the synchronization
The source of your tasks (Jira, Trello) and BigPicture App are synchronizing data. Depending on the setup, multiple scheduling BigPicture mechanisms may affect issue information (e.g., a strong dependency can reschedule a task and change its start/end dates). If you simply restore your Jira data, there is a chance that BigPicture scheduling mechanisms will immediately start updating your tasks.
Stopping the synchronization (temporarily setting the field mapping to Not synchronized) will give you time to perform a BigPicture restore without Jira data being affected.
Stop
Go to App Configuration > General > Fields.
Ensure all fields (for all projects) are set to Not synchronized. That includes the General mapping and Custom mapping settings (per project).
Make sure to adjust both the General synchronization settings and Custom synchronization settings (per project).
Do not forget to save the changes.
