After installing the JIRA connector to Bitbucket (both cloud instances) there is a webhook in BB that triggers a workflow transition when a pull request is created. However, there is no webhook when a pull request is merged or declined. This means that transitions associated with these events are not executed.
Then I tried adding my own webhook through the UI using the same address as the existing "JIRA" webhook (https://host/rest/bitbucket/1.0/repository/webhook) which gets fired on pullrequest:rejected and pullrequest:fulfilled. The requests are sent correctly and return with 204 but there is no reaction in JIRA.
Did anyone succeed in getting this to work? It seems like a very common problem.
When u create new own webhook to JIRA at same URL, look into Webhook log. In JIRA (readonly) there is
But in your own webhook this method is missing.
I have some problem.
As u can see in your cusmot webhook there is repo:push AND THEN pullrequest:fulfilled. Thast why in JIRA (readonly) PR merge/decline is not working. It will be done after next repo:push OR after sync JIRA with Bitbucket (manualy, or auto). Repo:push (commit, or create PR).
I send message to support 20/01/2017.
Do u fix this problem ?
P.S. I add trigger "commit create" to triger PR Merge. In Bitbucket repo with PR merge there is merge commit. Thats why it work. Byt this is cunning, not right way.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot