...
| Note |
|---|
This page is only available to Jira administrators. The feature is intended for backup purposes and is not recommended for transferring templates between different instances. |
On the Import/Export screen, you can export all the templates in your Jira instance into a .json file or import templates from a .json or .csv file.
...
Check out an example file and learn more about each parameter through the explanations below:
More Info Request | Hi $reporterName$, I'm reviewing this issue, and I don't think we have enough information to reproduce this problem. Can you add a little more detail to this ticket? Cheers, | GLOBAL | true | |
Not Supported Browser | Hi $reporterName$, We no longer support IE 7 in $projectName$. Alternatively, you can use the Chrome browser: Best regards, | PROJECT | SSP | |
Screenshot Request | Hi $reporterName$, Can you please add some screenshots of what you're seeing? Best regards, | USER | 557058:0c7dd459-31b7-4ef1-ae6c-a4a28ead7729 | |
Customer Timeout | Hi $reporterFirstName$, We haven't received any response from you for a while, so we assume that this issue has been resolved. However, if that's not the case, feel free to reopen it, and we will respond accordingly. Cheers, | GROUP | site-admins | true |
When importing a .csv file, it’s important to include headers as the first row. If the user skips the title, the first row of data will be shown as the title.
...
What If I Can’t Use the Atlassian Migration Program?
| Anchor | ||||
|---|---|---|---|---|
|
This feature is intended for backups only and is not recommended for migrating templates between Jira instances. If you can’t use the Atlassian Migration Program and need to import templates from Server, note the following:
Canned Responses for Jira Server does not have a notion of "GROUP" scope - it’s available only for the Cloud version of Canned Responses.
Canned Responses for Jira Server does not have a Quick toolbar - the "favorite" column will only be meaningful for Jira Cloud installations.
Jira Server has a different way of user identification than Jira Cloud. In server, it is still an userKey (i.e., "admin", "pstefaniak"), while in Jira Cloud it is accountId ("557058:0c7dd459-31b7-4ef1-ae6c-a4a28ead7729") - you will need to manually replace user keys for user IDs in the CSV.
Custom fields in dynamic variables are referenced by internal ID instead of a custom field name. It means that in different instances the templates might produce a different result, rendering different dynamic variables than expected.
You will have to change IDs of the projects and groups manually while transferring templates between instances (for Server-Cloud and Cloud-Cloud migrations).
| Anchor | ||||
|---|---|---|---|---|
|
...