You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?