JSM Workflow webhook no longer sends Issue ID in webhook payload for issues created via API or emai

[Scott Feit]

We have a JSM Workflow which contains a rule which triggers a webhook which initiates a JSM Automation. This webhook contains the Issue ID. However, as of October 10, the webhook no longer seems to contain the Issue ID, causing the JSM Automation to fail-- but only on issues which are emailed or created via API. Issues which are created via the portal allow the Issue ID to be sent successfully. Incidents created via email or API prior to October 10 had the Issue ID sent correctly. The reason I believe the Issue ID is not being sent is because the JSM Automation rule which receives the webhook returns "Search returned no work items" for issues created via email or API.

What could be the reason this process broke after October 10? And how can it be remedied?

[Marc -Devoteam-]

Hi @Scott Feit 

What is the web request being made in the automation?

Is this request based on the old search API endpoint, this endpoint is actively being disabled on instances.

See https://developer.atlassian.com/changelog/#CHANGE-2046 for the changes, if this is your case.

Otherwise, please provide:

1. what type of project is this (e.g., company-managed, team-managed, etc.), 

2. images that show your complete rule.

3. images showing the details of any relevant actions/conditions/branches.

4. images showing the Audit Log details for the rule execution.

5. Explain where the issue is.

These questions are not for not willing to help, but to have community members understand on how automation works.