We have a strange behaviour on vertigo SLA, basically we had a jira that was not in the scope of the jiras under SLA, we updated the criterias and then updated the ticket and the SLA has been computed.
The problem is that the due date calculated is correct but the SLA status is "delayed" whereas the time ellapsed between the creation date and the resolution date is < to the 480h of the SLA.
See screenshot and config export attached.
Applyed agreement types: Resolution
Applyed agreement times in that case: RTG-Incident-Internal