Two separate app versions were developed to meet the particular needs of our Clients and to overcome specific limitations of both Jira hostings. That’s why they differ from each other in terms of particular features and the overall application design. The Data Center version offers more advanced functionalities and customization options, while the Cloud version has been simplified and adjusted to the Jira Cloud experience.
Because of these differences, there is no dedicated migration tool that would allow the migration of settings between the two hosting options. We recommend carrying out the export and import process natively, using standard Jira features.
Feature
Data Center
Cloud
Template repository project
The repository project called Templates (TEMP) is created automatically during the app installation. It contains two predefined issue types (Template and Sub-template). It can also contain sample templates if you chose to add the samples during the onboarding. The repository project can be changed in the configuration.
The repository project is not created automatically unless you follow the onboarding. During the first steps you can choose an existing project or create a new one. The repository project can be changed in the configuration. In the Cloud version you can have multiple repositories.
Available under the Availability tab in particular templates and in the global Template Repository project’s settings. You can restrict the template’s availability to the following categories: Projects, Project Categories, Issue Type, Screens, Groups, Users, Languages.
Provides two types of variables: Dynamic (equivalent to User variables in the Data Center version) and Static (equivalent to System variables in the Data Center version). The functionality is basically the same, although the Data Center version offers more custom settings.
Autocomplete fields on Jira issue screens
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.
Applying templates to existing issues
Available under More on the issue view. See Apply template for more details.
Available under the three dots menu on the issue view. See Apply template for more details.
JQL Searchers
JQL queries dedicated for searching for templates. See JQL Searchers for more details.
Different JQL queries are available for the Cloud version. See JQL Searchers for more details.
Templates with subtasks
Supported with an additional workflow post function (Create Structure).
Supported when the Copy subtasks option is enabled in the template.
Templates for epics
Supported with an additional workflow post function (Create Structure).
Supported with no additional settings needed.
Templates with issue links
Supported with an additional workflow post function (Create Structure).
Supported with no additional settings needed.
Templates on the Customer portal
Supported with all functionalities such as autocomplete and variables. See Jira Service Management for more details.
Available under every project settings. See Default Template for details.
You can configure a default template for Jira Service Management for particular request types. See Default Template for details.
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.
Templates Navigator
A dedicated view for managing all the templates in the repository project. Offers additional features such as bulk editing, adding templates to categories, and more. See Template navigator for more details.
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.
Make sure your project that stores your templates is selected.
Issue Templates for Jira - Migration from Data Center to Cloud
Finish the migration following the Jira Cloud Migration Assistant wizard.
Result
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.
Template activation
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.
Warning
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:
Issue Templates for Jira - Migration from Data Center to Cloud
Single activation
You can activate the templates one by one manually using the toggle:
Bulk activation
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:
migrating templates from Jira Data Center to Jira Cloud.
If you have any templates in the repository that you don’t use, these templates will be also activated if you use this option.
Navigate to Templates Repository > Project settings > Issue Templates and open Manage templates tab.
Click Activate templates
Once you click it, the app will scan for all issues in the repository that are not activated as a template and automatically activate these templates.
Result
The manage templates list has been updated and all templates have been activated.
Template details’ configuration
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:
Template name. By default, the template’s summary becomes its name. You can change the name at any time if you want it to be different from the summary.
Scope (set of fields). After the migration, the template’s scope is set to inherit. This means that you only need to set the scope in an epic and it will be applied to the entire issue structure. The default scope is set to All fields except Reporter which means that even if you don’t configure the scope, all the template’s fields (apart from Reporter) will be copied to the target issue.
Availability. The availability settings are not inherited from the Data Center version but you can use the Create from template button instead. It suggests matching templates for the chosen issue type and is a good alternative for setting availability per issue type.
Migration FAQ
Do I need to configure any post functions on the Cloud version?
No, on Cloud you can autofill fields and copy values from templates without any post functions.
How do I copy subtasks on the Cloud?
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.
Will stories be copied under an epic?
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.
Can I use default templates on the Cloud?
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.
Need help?
If you can’t find the answer you need in our documentation, raise a support request.