Import Templates to Cloud | Smart Issue Templates for Jira Cloud

Import the templates-export-YYYY-MM-DD.json file created by the Data Center Manual migration export. Import scopes first, because templates refer to them.

This is part of the Manual migration (Alternative). To create the file, see Manual migration (Alternative) in the Data Center documentation. To migrate with JCMA instead, see Automated migration (Recommended).

How to Import Templates

Open Smart Issue Templates and select Templates > Issue Templates in the top menu
On Manage templates, open the More actions (...) menu and select Import
In Import templates, choose the templates-export-YYYY-MM-DD.json file

Review the preview. It shows how many templates are in the file, what will happen to each one, and anything that cannot be matched on this site

Click Import and keep the dialog open until it finishes
The result shows Templates have been successfully imported, or The import finished with some templates left with the reasons, then click Close

A file can hold at most 500 templates. A larger file stops with This file holds N templates. The most that can be imported at once is 500. Contact support if your export is larger.

What Is Carried

Field	How it is matched	If it cannot be matched
Name, description, tags	Copied as they are	-
Available for	Copied (scope or owner)	-
Project	By project key, then by name	Left empty, and listed in the preview
Work type	By name, within the matched project	Left empty, and listed in the preview
Scope	The imported scope from the same Data Center scope. The Data Center Global scope becomes the Cloud Global scope	-
Owner	By email, using the users listed in the file, then by display name	The user running the import becomes the owner
Summary, description, environment	Copied. Data Center wiki markup is converted to Cloud formatting	-
Assignee, reporter	By email, using the users listed in the file	Left empty, and listed in the preview
Labels, due date, time tracking	Copied	-
Priority, resolution	By name	Left empty, and listed in the preview

Not carried by the file import

These fields are always left out and listed under Fields the export could not carry:

Components
Fix versions and affected versions
Linked issues
Custom fields

The Automated migration (Recommended) carries the custom fields of a template. If your templates rely on custom fields, prefer the automated path, or set those fields again in Cloud after the import.

After the import

Open a few imported templates and check the project, work type and owner
Importing the same file again replaces the templates that changed and leaves the rest alone

See also Migrate from Data Center to Cloud for known limitations and frequently asked questions.