BETA Feature
This feature is currently in Beta and is only available to selected customers. If you want to participate in this Beta phase, please contact us via our support portal.
The results of the operation depends on different aspects such as the data to import as well as both your source and destination Jira instances. Do NOT delete the Checklist custom fields (server) or Checklist Definition (cloud) from the Jira source until you make sure that all the needed information was imported successfully.
In case of critical errors, the process may abort of freeze. In this event or any other unforeseen circumstances please contact us via support portal.
It is possible to import a checklist definition with all its checklists from the Server version of the add-on, or from another instance of the Cloud. For this operation you will need the data files generated with the Export feature of the Server or Cloud versions of the Okapya Checklist for Jira add-on.
To import a definition:
- Navigate to Settings > Apps > Checklist Definitions, and click the '+ Add definition' button:
- In the modal window switch to the 'Import definition' tab and click 'Import':
A new definition will be created, and you will see the files upload page. - Upload all data files, and then click the 'Start Import' button:
The page will show the import progress:
Depending on the number of imported checklists the operation may take from a few minutes up to a few hours. During the import process, on the issue view, you may see new checklists that are not yet available:
These are unavailable until the import process is completed in order to prevent data discrepancies.
When the import is completed, review the errors and warnings (if any), and then click 'Finish the import and enable the definition'.
Warnings and Errors
Please note that for the import process to be successful, the destination and source Jira instances should have the same:
- Project keys
- Issue type names
- Issue keys
In case of discrepancies, you may encounter the following messages:
Missing Context (Warning)
If some projects or issue types of the definition's context cannot be found in the destination Jira, you will see the following warning:
The definition will still be imported, but its context will be set to "All" in order to prevent accidental data loss. Please adjust the context manually after the import is finished.
Missing Issues (Warning)
If some issue keys cannot be found in the destination Jira, the corresponding checklists will not be imported. In this case you will see the following warning:
Other checklists, for which the issue keys were found, will be imported as usual.
Error
If an error occurs during the import process, you will see this:
Such an error usually means that the import process was affected severely. Significant data loss is possible, or the process cannot continue at all. In such cases please contact us via our support portal.