...
| Warning | ||
|---|---|---|
| ||
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. |
| Warning |
|---|
The results of the operation depend 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.
...
- Update your server instance with the latest version of Checklist Server. That will ensure that you have the latest version for the exporter and that the import will go smoothly.
- Export from the server, all the custom field contexts that you want to move to the cloud. Each exported context will create one or more files with the following name pattern customfield_<FIELD_ID>-<CONTEXT_ID>_<FILE NUMBER>. Group together the files where <FIELD_ID> and <CONTEXT_ID> are the same.
- Is is very important you ONLY upload files belonging to the same context (same <FIELD_ID> and <CONTEXT_ID>). Doing otherwise will lead to undesired and unexpected results and will result in having to redo the import.
- When uploading a custom field context from the server, the cloud will create a new Checklist Definition that will match the custom field context.
- If the context is limited to specific projects and that not all of those projects are found in the cloud, the Cloud Checklist Definition context will be marked as "All Projects" and/or "All Issue Types".
- Some features from server are not exported (assignee, priorities, due date, advanced markdown, access permissions)
- Cloud does not support headers section yet. So headers are exported as normal checklist items.
- Statuses are not on a per checklist definition like on the server. So all statuses are exported to the Status page and will be visible to all issues. It is therefore best to ensure that similar statuses are renamed exactly to identical names on the server before being exported.
- If you migrate in steps, make sure that you only select specific projects during the server export.
- If, during the import, some projects are not found, all the checklists for these issues will be skipped.
- The import can be a long process so please be patient. Each import is placed in a queue and we process one import at a time. So depending on the number of people trying to import and the size of the import, it can take hours to even days.
...
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.