...
creating a sample service project , or
creating SLAs in your destination project matching the missing SLA-type custom fields
...
To create new SLAs in an existing service project on the destination, you need to go to the Project settings > SLAs and type a new SLA name, as shown in the screenshot below. Afterward, you’ll your Jira Cloud site will have a custom field with that name in your Jira Cloud site.
...
Case-sensitivity by SLA-type field names
...
Jira Service Management configuration | Migration with Cloud Migration Tool | ||||||
|---|---|---|---|---|---|---|---|
Service Management project basics |
| ||||||
Organizations |
Organization membership isn’t migrated. If a source organization has 2 users in it, the same organization migrated to the destination will have 0 users in it. | ||||||
Requst types |
| ||||||
Portal groups |
For now, we support the creation of request-type groups , but not the update. | ||||||
Portal settings |
| ||||||
SLAs |
Not available due to restrictions by Atlassian’s APIs. | ||||||
Queues |
| ||||||
Calendars |
| ||||||
Email requests |
| ||||||
Forms |
| ||||||
Satisfaction settings |
| ||||||
Access settings |
| ||||||
Customer permissions |
| ||||||
Customer notifications |
| ||||||
Attachment security |
| ||||||
Sender names |
| ||||||
Templates (Premium Jira Cloud Only) |
| ||||||
Language settings |
| ||||||
Knowledge base |
| ||||||
Knowledge base labels |
| ||||||
Knowledge base enabled request types |
| ||||||
Reports |
| ||||||
Widgets |
| ||||||
Automation rules |
|
...