To import an SLA configuration:
| Button handy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Button handy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
This page is about Time to SLA for Jira On-Prem. Using Jira Cloud? Click the Cloud button above. |
This page will show you how to import SLAs and calendars from one instance to another.
| Note |
|---|
Keep in mind that there is no issue SLA transfer system for SLAs and calendars that are transferred with Import. This means that, when you export and import your SLAs from one instance to another, you’ll need to recalculate all of your SLAs to see them on your existing issues. If you have high volumes of SLAs, this can be problematic, which is why we recommend you use Jira Cloud Migration Assistant if you want to transfer your issue SLAs. |
To import SLAs and calendars into your instance:
1. Go to Import/Export on the sidebar, and click Import.
...
2. Select the Backup Type. This can be Legacy SLA(s) or Next-Gen SLA(s).
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
This only states whether your backup contains Legacy or Next-Gen SLAs. The import process will create Next-Gen SLA(s) for all backup types. |
3. Upload the file (in .json format) you want to import
...
.
...
4. Select how you’d like to merge imported configurations with existing ones.
...
5. Select
...
the components you want to import.
...
6. Match the Project(s), Group(s), and Status(es) in the import file with what you have in your instance.
...
7. On the Summary screen, check if there are any mistakes in your selections. After you make sure everything is as it should be, click Import.
8. Once the process is done, it will look like this, and the imported configurations will appear on your related screens:
...
| panelIconId | atlassian-warning |
|---|---|
| panelIcon | :warning: |
| panelIconText | :warning: |
| bgColor | #FFEBE6 |
...