| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Preparation
Install STAGIL Issue Templates onto the Cloud instance you chose to migrate to.
Install the Jira Cloud Migration Assistant tool on your Server | DC hosted instance. Read this guide https://www.atlassian.com/migration/plan/cloud-guide#migration-tools and proceed with your migration path according to the recommendations.
See our Cloud vs. Data Center feature comparison to become aware of differences in the template configuration.
Migration
STAGIL Issue Templates support automated migration. To migrate the templates mark the app ‘Needed in Cloud’ during the app assessment stage of the migration.
Post-migration
We worked hard to preserve and maintain app functionality in Cloud the same as in the DC version of the app. There are, however, some differences, as well as improvements. Please review the documentation for Issue Templates Cloud in order to adapt to the changes more quickly.
Post-migration
We worked hard to preserve and maintain app functionality in Cloud the same as in the DC version of the app. There are
...
, however, some differences, as well as improvements. Please review the documentation for Issue Templates Cloud in order to adapt to the changes more quickly.
We have also collected some key points on configuration migration specifics:
Subtask templates
Issue Templates for Jira Cloud do not currently support templates for issue type ‘Subtask’. Such templates will not be migrated.
Template viewing permission
All templates will be migrated with ‘Viewers’ permissions set to ‘Private’.
Template editing permissions
Issue Templates for Jira Cloud do not have the ‘Editors’ feature. This does not prevent migration and the templates will be migrated regardless.
Context
If template context fields such as ‘Project categories’, ‘Project’ or ‘Issue types’ have no value, after migration new templates will have global values set for empty context fields.
Template context in Cloud does not include ‘Project Categories’. If this field had value, after migration, all projects that have been included in the category, will be set as values in the ‘Project’ context field.
Supported fields
Group picker fields (single & multi) are not supported in Issue Fields for Jira Cloud. If these fields are included in the template, they will be omitted, and templates will still be migrated as expected.
Template configuration: default values for ‘Assignee’ & ‘Reporter’ fields
This configuration is not available in Could. If the checkbox ‘Current user’ next to the ‘Assignee’ & ‘Reporter’ fields is checked out the fields, the templates will be migrated, but without these fields.
Create & Link button configuration: multi-create mode
Issue Templates for Jira Cloud do not include multiple issues create mode for Create & Link buttons. Buttons will still be migrated.
Create & Link button configuration: Link Target
The ‘Link Target’ configuration is not available for buttons in Cloud. If Parent issue or Parent Epic is selected, then all buttons will be still migrated, with the current issue being a default link target for all buttons in Cloud.
Create & Link button configuration: Behaviour
‘Behaviour’ configuration is not available for buttons in Cloud. Buttons with such configuration will still be migrated.
