Migration from Server to Cloud

Overview of Issue Templates for Jira Server and Cloud

While considering migration from Jira Server to Cloud, it is recommended to consider differences in features offered by apps for these hosting types.

While Issue Templates Server and Cloud both offer a variety of versatile features to boost performance and increase agility, as described in Why people use and love Issue Templates for Jira, both app functionalities and configurations differ significantly between the two hosting types.

Perhaps one of the most significant differences, caused by current Jira limitations, is that in Issue Templates on Cloud, the Autocomplete feature on the Create Jira screen is unavailable. Instead, a dedicated button for Issue Templates is created.

Another Server feature currently missing from Cloud due to Jira limitations, is Default templates.

A benefit of Issue Templates for Jira Cloud is that there is no need to use workflow post functions. Subtasks and Issues under Epics are copied automatically.

When it comes to similarities, the following popular features are available both for Server and Cloud, although their configurations may differ:

• Templates with subtasks
• Templates for epics
• Static and dynamic variables
• Apply template
• Issue links

For a demo of Issue Templates Server, check out Work Smarter, Better and Faster with Issue Templates for Jira Server.

For a demo of Issue Templates Cloud, check out How to Create Epic Issue Templates in Jira Cloud. For more details, see Issue Templates Cloud documentation.

Keep in mind, that there is currently no direct migration path for app data and configurations from Server to Cloud.

Moreover, you will also need a separate license for a Cloud app.

For more information on migrating from Jira Server to Jira Cloud, see Atlassian documentation.