.png)
Smart Issue Templates offers two ways to bring your scopes, templates and hierarchies from Jira Data Center to Jira Cloud. Start with the automated path, and use the manual path if the automated one cannot complete or is not an option for your site.
Automated migration - Recommended
Smart Issue Templates is part of your Jira Cloud Migration Assistant (JCMA) migration plan. Its data arrives in Cloud automatically, matched to the projects and users migrated with it. You follow it on the Migration status page, and running it again updates what it created instead of adding copies.
Automated migration (Recommended)Manual migration - Alternative
You export files from Data Center, one per kind of data, and import them here. Use it when JCMA cannot complete the migration, when JCMA is not an option for your site, or when you want a copy of your data you can keep.
Manual migration (Alternative)The Data Center side of both paths is documented in Migrate to Cloud (Data Center documentation).
Before Either Path
-
Update Smart Issue Templates to the latest version: 3.1.9 or higher (Jira 10 and below) or 4.0.5 or higher (Jira 11) on Data Center, and 28.0.0 or higher on Cloud.
-
Make sure the projects, work types, groups and users your data points at are on the Cloud site.
-
Pick one path for each kind of data. Records created by one path are not matched to records created by the other, so using both can create copies.
Which Path Should I Use?
|
|
Automated migration |
Manual migration |
|---|---|---|
|
How it runs |
Inside your JCMA migration plan |
Export files from Data Center, import them in Cloud |
|
Data |
Scopes, templates and hierarchies |
Scopes, templates and hierarchies |
|
Project or work type missing in Cloud |
Scopes and templates that use it are not migrated. Hierarchy levels are kept and marked Incomplete |
The item is imported without it. Hierarchy levels are marked Incomplete |
|
Owners |
Matched through JCMA; otherwise a site administrator |
Matched by email for templates and hierarchies; scopes get the user running the import |
|
Template custom fields |
Carried, for the supported field types |
Not carried (neither are components, versions or linked issues) |
|
Size |
No per-file limit |
Up to 1,000 scopes, 500 templates and 100 hierarchies per file |
|
Progress |
Migration status page in Cloud, JCMA log and Cloud Migrations page in Data Center |
Preview and result in the import dialog |
|
Running it again |
Updates what the previous run created |
Replaces the entries that changed, leaves the rest alone |
Known Limitations
-
Projects and work types: they must exist on the Cloud site. Over JCMA, a scope or template that uses a project that was not part of the Jira migration is not migrated.
-
Hierarchy levels: a level whose project or work type is not on the site is kept with that value empty and marked Incomplete, on both paths.
-
Hierarchy reporter: the reporter of a level is not carried, unless it is a dynamic reporter.
-
Hierarchy settings: the automated path does not carry the scope and available for settings of a hierarchy. Set them again in Cloud.
-
Template fields in the file import: custom fields, components, fix and affected versions and linked issues are not carried by the manual path.
-
Scope owners in the file import: the user running the import becomes the owner.
-
File size: the manual path imports at most 1,000 scopes, 500 templates or 100 hierarchies per file.
-
Users: owners that cannot be matched fall back to a site administrator (automated) or to the user running the import (manual). An owner shown as Migrated User can be changed in Cloud.
Frequently Asked Questions
Will my hierarchies come across?
Yes, on both paths, with Smart Issue Templates 3.1.9 or higher (Jira 10 and below) or 4.0.5 or higher (Jira 11) on Data Center and 28.0.0 or higher on Cloud. Each hierarchy arrives with its levels and the issue content of each level. Levels whose project or work type is not on the Cloud site are kept and marked Incomplete, so nothing is silently lost. The reporter of a level is not carried, and with the automated path the hierarchy's scope and available for settings need to be set again in Cloud.
What happens if a work type is missing on the Cloud site?
For a hierarchy, the level is kept with an empty work type, marked Incomplete, and the work type is listed as Work types this site does not have. For a scope or template over JCMA, the item is not migrated and the Error log names the work type. With the file import, the work type is left out and listed in the preview. Create the work type in Cloud and run the migration or the import again.
Can I run the migration again?
Yes. The automated path updates what the previous run created, and the file import replaces what changed. Neither creates copies, as long as you stay on the same path.
The automated migration does not complete. What now?
Check the Error log on the Migration status page, and the Cloud Migrations page in Data Center. If the problem persists, use the Manual migration (Alternative) for the data that did not come across, or contact support.
Do I need to enable a setting before migrating?
No. Both paths only need the latest app versions and a Jira administrator.
My export has more than 100 hierarchies (or 500 templates, or 1,000 scopes)
Use the automated path, which has no per-file limit, or contact support for help with the file import.
Getting Help
Contact us via the Customer Portal. For the automated path, include the migration ID, the JCMA log and the migration data exported from the Support menu on the Migration status page. For the manual path, include the exported files and the result shown by the import.