Structure Plugin for JIRA - Version 1.2

Index

Child pages
  • Restoring Structure from Backup

This documentation relates to an older version 1.2 of the Structure Plugin for JIRA. View the current documentation home.

Skip to end of metadata
Go to start of metadata

Restoring structure from backup brings back the structures created at the moment of backup. However, if Structure database is not empty, the restore can be used to merge existing data with the data taken from backup.

Restoring structure will not affect issues in any way. The issues that make up the hierarchy should already exist in JIRA. If you do full restore, then you need to run the standard JIRA data restore first - see Structure Backup and Restore. 

To restore the structure from backup:

  1. Navigate to Administration | Structure | Restore Structure.
  2. Enter the full path to the structure backup file (either .xml or .zip).
  3. In case current Structure database is not empty, you'll see the additional option: Clear Structure Data Before Restoring from Backup. If you leave it unchecked, the data from the backup will be merged with the existing structure data. If you check the Clear option, the current structure data will be wiped before restoring from backup.
  4. Click Restore.
  5. If you chose to clear the current database, confirm the operation. It cannot be undone! 

After the structure has been restored, open Structure | Manage Structure page to see if the structures are there.

You also can restore structure data from backup files made with the earlier versions of the Structure plugin. 

How Existing Structure Data is Merged with the Data from Backup

  1. Structures are merged by the structure ID. If a structure in backup and a structure in the database have the same ID, they are merged.
    1. Structure merged by consequently adding issues mentioned in the backup structure (referred to by numeric issue ID) to the existing structure at the correct positions. If such issue already exists in the database structure, it is not added but rather moved to the required position - with all sub-issues, if there are any.
  2. Synchronizers are merged by the synchronized ID. If a synchronizer with given ID already exists, it's not changed. If there's no synchronizer with such ID, it is installed.