Summary

When a Jira issue workflow changes the create transition event to either a "generic event" or "custom event", Forge applications receive the wrong event type. Instead of receiving `avi:jira:created:issue`, they receive `avi:jira:updated:issue`.

As a result of receiving the incorrect event type, Forge apps cannot properly identify that an issue was newly created.

When an issue is created, Forge apps should receive `avi:jira:created:issue` event regardless of whether the workflow uses:

• Default issue created event, or
• Generic event, or
• Custom event

Steps to Reproduce

1. Create a Jira workflow with a create transition
2. Configure the create transition to use either:

• Generic event, OR
• Custom event
  3. Install/deploy a Forge app that listens to `avi:jira:created:issue` events
  4. Create a new issue using this workflow
  5. Observe that the Forge app receives `avi:jira:updated:issue` event instead

Additional Notes

The behaviour is also inconsistent if compared with Jira automation

• In Jira automation, Custom events in "issue create" transition triggers the "Issue Created" trigger
• in Forge, Custom events in "issue create" transition triggers the "Issue Update" `avi:jira:updated:issue` trigger