-
Bug
-
Resolution: Fixed
-
Low
-
2
-
Severity 3 - Minor
-
Issue Summary
When the default event fired by the "Fire event" post-function is changed in a workflow transition, any related webhook(s) is not fired.
For example, the initial transition (issue creation), by default fires an Issue Created event, saying: "Fire a Issue Created event that can be processed by the listeners."
If the post-function is updated to fire something other than the Issue Created event (for example, a custom event), then jira:issue_created webhooks will not be sent by Jira when issues are created in projects that use the modified workflow.
This works in a similar way for any other transition and the jira:issue_updated webhooks.
Steps to Reproduce
- Edit the post-function to fire a different event
Expected Results
Any relevant webhook is sent by Jira.
Actual Results
Webhooks are not sent by Jira.
Workaround
The workaround is to restore the default event in the workflow post-function:
- Create Issue for the initial transition
- Generic Event for any other transition
- is related to
-
ECO-395 Forge Jira events are not triggered when Custom Events Notification are configured in Workflow Post Function
-
- Gathering Impact
-
- was cloned as
-
JRACLOUD-83784 Changing the default event fired by 'Fire Event Function' post function to a different system event prevents webhook from being sent or sends incorrect webhook
-
- Closed
-