Canned Responses Pro Server/DC to Cloud migration
- Derya Özdemir
- Iryna Ihnatiuk
Here is what you need to know about migrating your Jira Server instance with Canned Responses Pro Templates for Jira to Jira Cloud.
1. Your templates will be migrated with Jira
Your Canned Responses' templates will be migrated automatically along with Jira data if you follow Atlassian's Cloud migration guide. Canned Responses app will appear in Jira Cloud Migration Assistant to allow a smooth data transition.
Automatic app data migration will be available as soon as Atlassian enables app migrations in Jira Cloud Migration Assistant.
2. You may need a browser extension
Though it's not mandatory, we highly recommend using a dedicated browser extension for the best experience with Canned Responses.
The extension makes it possible to use templates directly from Jira's native text fields so the user doesn't even notice that templates are served by Canned Responses Pro Templates for Jira.
Canned Responses can be used without the extension; however, in that case, templates are only accessible via a separate comment box.
Such differences are dictated by the current limitations of Jira Cloud platform – at the moment, it's impossible to integrate with Jira's native fields through API.
Please check out the gifs provided below to understand the described differences:
Jira Server | Canned Responses is embedded directly into Jira's comment field.  |
Jira Cloud with Extension | Canned Responses is embedded directly into Jira's comment field – just like in Jira Server.  |
Jira Cloud | Canned Responses is available through a separate comment box. |
What you might want to do:
Let the users in your organization know that they can use Chrome, Firefox, or Edge browser extensions for the best experience with Canned Responses.
3. You will not have to use syntax to style templates
Jira Server uses the old Jira issue view that comes with legacy text formatting. Your current templates are most probably written in old wiki syntax.
In Canned Responses for Jira Cloud, the templates can be created in a built-in visual editor with no need to use the syntax (but with optional support for the new markdown). All of your existing templates will be converted to the new format.
What you might want to do:
Check if your migrated templates are rendered properly on your new Jira Cloud instance.
If formatting requires updating – edit and save them manually using the editor.
4. There are some differences in features
There are some minor differences in terms of user interaction and functionality, mostly in favor of the Cloud solution. Check out the table for a detailed breakdown:
 | CR Server/DC | CR Cloud |
|---|---|---|
Project type | All | All |
Rich text editor | ||
Dynamic variables | ||
Attachments | ||
Mentioning | ||
Grouping | Visibility scope | Visibility scope + folders |
Permissions customization | Groups, role | Groups, role, project |
Visibility scope | Personal, single project, global | Personal, multiple projects, groups, global |
Save comment as a response | ||
Transition screen | ||
Export/Import templates | ||
Example templates | ||
Support Description | ||
Text field support | ||
Workflow post function | ||
Queues | ||
Text Assistant | Â | |
Automated actions | Â | |
Signatures | Â | |
Insights | Â | |
Template search/filters | Â | Â |
Favourite responses | Â | |
Scheduled comments | Â | |
Replace response | Â | |
Inserting initial template | Â |
What you might want to do:
Consider giving your team a quick tour of Canned Responses or send them this page as the instruction.
In case you need help, please get in touch and we'll be happy to introduce your team to Canned Responses.
5. Your global settings will not be migrated
You will have to set global settings (project and user permissions) anew on your Cloud instance.
6. We are here to help
In case you need any guidance or help during your migration process, please do not hesitate to contact us – we'll be glad to help! We'd also love to listen to your organization's specific needs, so we can adjust product development plans.