SLA will not be triggered if custom events are used as the event to be fired upon issue creation

Problem Definition

SLA doesn't get triggered upon issue creation if the generic Issue Created event is not fired.

Steps to Reproduce the Problem

1. Create a Service Desk project from the Sample Data.
2. Go to JIRA Administration > System > Events, add a new custom event with the "Issue Created" template.
3. On the header, click on Projects > Service Desk project > Project settings > Notifications, add the custom event.
   • Click on Actions > Edit notifications > Add notification.
   • Select the custom event and assign it to the Reporter.
4. On the header, click on Projects > Service Desk project > Project settings > Workflows.
5. Edit the workflow for Incident and Service Request.
6. Switch the workflow to Diagram mode, click on the Create Issue transition.
7. On the small windows that appear with some options, click on Post Functions.
8. Edit the post function of Fire a Issue Created event that can be processed by the listeners. and replace the event with the custom event created from step 2.
9. Publish the workflow.
10. Create a test issue from the Customer Portal.

Expected Result

The SLA counter will show up in the issue with the started Time to first response and Time to resolution.

Actual Result

• No SLA counter will show up in the issue with the started Time to first response and Time to resolution until an SLA recalculation.
• After every issue creation, an Update button below SLAs in the project settings menu will be visible for SLA recalculation, as if the SLA metrics have been edited.

Workaround

• Use the generic Issue Created event in the workflow transition for issue creation AND
• Add the Issue created as one of the conditions to start counting time for SLA