SLA is placed in an incorrect state when a custom listener transitions an issue that changes the SLA state

Problem Definition

Administrators can create custom listeners to respond to events fired by Jira, per https://confluence.atlassian.com/adminjiraserver/listeners-938846909.html.

When such a listener is used to transition a Jira Service Desk issue in response to an event, and that transition is responsible for changing the SLA state of the issue, the issue will remain in the original SLA state, rather than the new state for the new status.

This is due to a race condition between how the listener handles an event (i.e. the CommentCreatedEvent) earlier than when Jira Service Desk itself does, which results in Jira Service Desk returning the SLA state to the old state which is incorrect for the new status.

Suggested Solution

Unknown. Allow for Jira Service Desk to recognize that a transition has occurred prior to it's own event handling.