previously we used the issue_updated event and the issue changelog to call a function when issue.status changes from `To Do` -> `Not Doing`(custom status).
Now, only noncustom(original) events trigger the webhook
IE:
`Not Doing` -> `To Do`
`New` -> `In Progress`
`Progress` -> `Competed`
but not original status -> custom status (custom status are: Deployed, Not Doing)
IE:
`To Do` -> `Not Doing` does not trigger webhook
`Completed` -> `Deployed` does not triggerwebhook
is this intended behavior?
extra: is there a way to limit versioning of jira webhook events? the api changes every months and ends up breaking the layered behavior attached to the hook.
In the post-function of the workflow transition (TO do > "Not Doing") it's generally a "Generic event" which is triggered. "Issue Update" events are triggered when you change value of a field on the issue, thus triggering issue update event.
For workflow transition you can add post-function to trigger "Issue update" event instead of "Generic event" if you have listeners configured for the "Issue update" event.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Issue_Updated event does not fire, when status changes. You need to add Trigger a Webhook post function to the required transactions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.