Forge avi:jira:created:issue trigger not firing for JSM requests with multiple inline images

[f_rancisco]

I am building a forge app that listens to jsm issue creation (avi:jira:created:issue) to trigger a workflow. I'm seeing inconsistent behavior depending on how the request is created:

- When creating a request with 1–2 inline images in the description, everything works as expected:

1. jsmIssueCreated trigger fires
2. app processes the issue

- When creating a request with more than two inline images:

1. the issue is created in JSM
2. no Forge logs are generated
3. the jsmIssueCreated trigger does not fire
4. app logic is never executed

It looks like there may be a difference in how JSM processes requests with multiple inline images. With a small number of images, everything happens in one step. With many images, it seems like the process might be handled differently (possibly in stages), which could be affecting when or if the event is sent to forge.

Has anyone experienced this with requests containing multiple inline images?

[Ajay _view26_]

Hi @f_rancisco 

The documented behavior is that avi:jira:created:issuefires when an issue is created, but based on your symptoms I’d be careful about assuming JSM request creation with many inline images is always a single-step operation.

My guess is that larger rich-content submissions may be causing follow-up processing after the initial request creation, and your app is effectively depending on timing that is stable for small requests but not for larger ones.

Practically, I’d test two changes: subscribe to both avi:jira:created:issue and 
avi:jira:updated:issue, and have the handler re-fetch the issue details instead 
of trusting the initial event alone. 

If the created event truly never arrives for that case, that sounds more like a Forge/JSM bug than expected behavior, and I’d raise it with Developer Support because Atlassian’s docs do say the event should be sent when an issue is created.