Learn about migrating templates from Jira Data Center to Jira Cloud
Both versions of the Issue Templates app enable rapid issue creation using predefined templates. Core functionalities are available in both Jira Data Center and Jira Cloud, delivering the same business value.
The Cloud version introduces a streamlined UI tailored to its environment, including a template creation wizard and AI-powered support. While the Data Center version currently offers more advanced capabilities, we’re continuously closing the gap with ongoing improvements to the Cloud edition.
Migration involves two steps: exporting/importing templates and configuring settings manually. Jira’s native export/import tools support the first step. Due to platform-specific differences, a dedicated migration tool is not available.
Feature | Data Center | Cloud | DC details | Cloud details |
---|---|---|---|---|
Multiple projects as a template repository | You can only have one repository. The app offers sample templates. | You can establish multiple repository projects and use an easy onboarding. You can use existing projects as repositories or create new ones. | ||
Advanced template configuration | Available on the template’s issue view, as well as in the Template Navigator. | Available on every template’s issue view in a repository project. Offers an easy template configuration wizard, see Template’s configuration. | ||
Static variables | There are two types of variables: User variables and System variables. | You can add Static variables that are equivalent to system variables in the Data Center version. | ||
Dynamic variables | - | New Dynamic Variables. | ||
Template selection on the native create screen | Available for all screen types delivered by Jira, including create, edit and transition screens. | You can automatically add the template select field to Jira native create screen. See more details in the Create from template chapter. | ||
User-friendly template creation wizard | Templates are configured on the template’s issue view, as well as in the Template Navigator. | Offers an easy template configuration wizard - Template’s configuration. | ||
Smart defaults | - | Provides a new feature - Smart Defaults which are configurable template fields that automatically calculate and fill in values using smart expressions at the moment an issue is created, enabling automation and dynamic data population. | ||
JQL Support | Offers the same functionality - see JQL Searchers for more details. | Offers the same functionality - see JQL Searchers for more details. | ||
Automation and app integration | The way the app is integrated differs. For more details, see REST API | The way the app is integrated differs. For more details, see Automation. | ||
AI assistant | - | You can use Deviniti’s Rovo Assistant with this application. | ||
Simple availability settings | Available under the Availability tab in particular templates and in the global Template Repository project’s settings. | Available in the Template’s configuration panel in Availability tab. | ||
Advanced availability settings | You can restrict the template’s availability to the following categories: Projects, Project Categories, Issue Type, Screens, Groups, Users, Languages. | Allows to restrict the template’s availability to particular projects only. | ||
Set of fields/Scope | Available on every template’s issue view (Fields tab) and under the repository project’s settings. | Available on every template’s issue view, under the repository project’s settings and global configuration. | ||
Customer portal support | Supported with all functionalities such as autocomplete and variables. See Jira Service Management for more details. | Supported with limitations. See Jira Service Management for more details. | ||
Templates with epics/subtasks/issue links | Supported with an additional workflow post function (Create Structure). | Supported with no additional settings needed. | ||
Use as a template | You can convert any issue into a template. See Use as a template for details. | You can convert any issue into a template in every Repository project. | ||
Default templates | Available under every project settings. See Default Template for details. | You can configure a default template only for Jira Service Management for particular request types. See Default Template for details. | ||
Bulk actions | You can edit and manage templates in bulk, rather than template by template. | You can edit and manage templates in bulk, rather than template by template. |
To perform the migration you’ll need two separate licenses, one for the Data Center version and one for the Cloud. Read more about Dual Licensing.
You can check official Atlassian documentation for migration details.
If you have some questions regarding Jira contact Atlassian support selecting Migration Support.
In both versions, templates are stored in a project that serves as a repository. This project can be migrated, just as any other project, using Jira’s native importing tools.
In Jira Cloud, a template is just an issue with additional issue properties. Unfortunately, at the moment there is no easy way to migrate issue properties. After importing the repository project, all the issues should be visible in issue navigator, however they may not be visible as templates on the Manage templates page yet.
Your template repository project along with templates has been migrated, however you still need to activate them and recreate some features manually, such as certain types of variables.
After the migration, the template issues are available in the repository project but they still need to be activated as templates for Jira Cloud. In order to do so, you need to use the Use as a template setting in each template issue.
If you migrate templates to a Jira Cloud instance where Issue Templates is already installed, and you are experiencing problems with app permissions, we recommend to reinstall the app. It should fix the problems with permissions automatically.
After the activation, all the templates will be available on the Manage templates page in Jira Cloud:
You can activate the templates one by one manually using the toggle:
You can activate all templates that have no configuration and have the Use as a template toggle disabled. You should use this option right after migration.
Use bulk activation after:
Templates will be activated and configured with default values from the template configuration panel:
See Template Configuration for details.
If you have any templates in the repository that you don’t use, these templates will be also activated if you use this option.
The manage templates list has been updated and all templates have been activated.
An activated template is practically ready to use on the Cloud. Fields and their contents are preserved in each template. You might want to additionally configure the following:
No, on Cloud you can autofill fields and copy values from templates without any post functions.
The Copy subtasks feature is enabled by default. Every template issue that has subtasks will create those subtasks in the target project without any additional configuration. However, you may need to select that option in child issues if you want to copy sub-tasks there as well. See Copy subtask for details.
A template name is replaced with summary in the Cloud version.
Yes. If you have a template that is an epic with stories, the entire structure will be created in the target project without any additional configuration.
Variables in the Cloud version work from a technical point of view, in a different way than in the DC version. Therefore, it’s necessary to configure them again.
If you try to migrate your templates that are based on the template issue type it might disturb your migration process, if you don’t have this issue type added in your Cloud project.
Because of the Jira API’s limitations, currently we are not able to offer a Cloud alternative for this feature.
You can reach a similar effect (although without the autocomplete feature) by adding the Apply template post function to the Create transition.
This feature is on the roadmap and will be added to the Cloud version.
If you can’t find the answer you need in our documentation, raise a support request.