How does migrating Jira Cloud affect my existing SLAs

[Michael Wheatstone]

We are planning our migration to cloud from an on-prem server instance and one thing the documentation is not clear on is what happens to our Jira service management SLA's on currently active tickets when we migrate.

For example, Issue SUP-1563 has an active SLA, the duration of the SLA is a P4 (4 weeks), and there is currently 2 weeks left on the SLA.

When we migrate to the cloud, if all of the SLA calendars and rules are setup identical to those on the old server instance will Issue SUP-1563 show that it is on a P4 (4-week SLA, and will it still retain the information that it only has 2 weeks left before the SLA expires?

Or will all Issue lose its data on the amount of time that has expired on the SLA? 

[Iana]

Hi,

All SLA data is properly migrated towards Cloud. If your issue SUP-1563 has a goal of 4 weeks and has 2 weeks left at the moment of migration, it will have 2 weeks left after migration (technically 2 weeks minus the time it took you to go live after the migration if it happens during working hours). 

Say you have an issue that expires on friday at noon and you start your migration on a monday at 9AM and it takes you 1 day to get your new Cloud instance to go live. Your issue will still expire on friday noon (the SLA doesn't stop just because your instance in unavailable).

It might be a good idea to set the migration downtime as non-working in your SLA calendar in order not to penalize your teams.