Issue Summary

The current SLA calculation optimization logic will skip sla recalculation if there are several updates to the issue at the same time. This might lead to missing critical events being missed (ISSUE_MOVE).  As a result, work item might end up having "ghost" sla running in the background leading to these items appear wrongly in JQL function like breach(), everbreach() when they shouldnt.

Steps to Reproduce

1. Create 2 projects - SRC and DEST , both with SLA "Time to first response" with a default duration of 5m
2. Create a work item in SRC project 
3. Create an automation rule to make the several update to the work item and also move it to project DEST
4. Make change to the work item to resolve the "Time to first response" and ensure it's completed within the time target
5. Use JQL search "Time to first response" = breached()

Expected Results

Work item to not appear in the search result.

Actual Results

Work item appears even though the "Time to first response" SLA was not breached. 

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available