SLA calculated incorrectly when you change issue type of an issue and the SLA cycle has completed

Summary

SLA calculated incorrectly when you change issue type of an issue and the SLA cycle has completed

Steps to Reproduce

1. Create an SLA Time to first response that looks as follows, one of the SLA stop condition should be Resolution Set
   
2. Create another SLA metric Time to resolution that looks like below, one of the SLA stop condition should be Resolution Set
   
3. Create an issue of type IT Help, it will be created with an ongoing SLA Time to first response with target 7h30m
4. Change the issue type to something other than IT Help but uses the same workflow, the SLA will accordingly get updated to an ongoing SLA Time to resolution with target 336h
5. Try to change the issue type a few times, the SLA information is still updated correctly as per the issue type
6. Now with an issue type, IT Help and ongoing SLA Time to first response with target 7h30m, resolve the request by setting Resolution field after 5 minutes, an SLA stop condition for both the SLA's
7. The SLA will be Time to first response with completed at 7h25m 
8. Now change the issue type from IT Help to some other issue type after two minutes
9. The SLA information will still be reflected as Time to first response with completed at 7h25m when it should be updated to a completed cycle of Time to resolution 335h55m due to issue type chnage  

Expected Results

SLA information is displayed correctly

Actual Results

The SLA information is in an inconsistent state

Workaround

Execute the SLA recalculation endpoint to correct the SLA information 

• SLAs in Jira Service Desk Cloud are missing or disappear