Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira Webhook Events issue_updated does not cover custom Status values?

qwertyzone March 26, 2018

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.

2 answers

0 votes
Tarun Sapra
Community Champion
March 26, 2018

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.

qwertyzone March 26, 2018

thanks so much! y'all are awesome.

0 votes
Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 26, 2018

Issue_Updated event does not fire, when status changes. You need to add Trigger a Webhook post function to the required transactions.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events