Canned Responses are embedded directly into Jira's comment field
Canned Responses are embedded directly into Jira's comment field – just like in Jira Server
Canned Responses are available through a separate comment box
Here is what you need to know about migrating your Jira Server instance with Canned Responses Pro Templates for Jira to Jira Cloud.
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 apps migrations in Jira Cloud Migration Assistant. |
We recommend using a dedicated browser extension for the best experience with Canned Responses. Though it's not mandatory.
Such differences are dictated by current limitations of Jira Cloud platform – it's impossible to integrate with Jira's native fields through API at the moment.
Please check short videos provided below to understand the described differences:
| Jira Server | Canned Responses are embedded directly into Jira's comment field | |
| Jira Cloud with Extension | Canned Responses are embedded directly into Jira's comment field – just like in Jira Server | |
| Jira Cloud | Canned Responses are 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 extension for the best experience with Canned Responses.
Jira Server uses 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 built-in visual editor with no need to use the syntax (but with an 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 update – edit and save them manually using the editor
There are some minor differences in terms of user interaction and functionality, mostly in favor of Cloud solution:
Cloud version comes with interaction improvements - better templates search, folders navigation etc.
|
In Cloud, it is possible to star templates as favorite. That makes them available through shortcuts (non-extension version only)
 |
There are additional Settings options available in Cloud – for example ability to define default template (non-extension version only)
|
Customisable Signatures for Responses - Create and manage signatures. Use dynamic data for each user and project. Set flexible rules – define global, per-project and personal signatures. Optionally, restrict to “Reply to customer” in JSM. Learn more
|
New built-in visual editor for creating and editing templates - with most popular styling options and optional support of the new markdown syntax
Canned Responses in Cloud are currently only available for Comments and Description fields
Autocompletion feature for inserting templates (quick search accessed with $ shortcut) is no longer available in Cloud
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
You will have to set global settings (project and user permissions) anew on your Cloud instance.
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 about your organization's specific needs, so we can adjust product development plans.
