The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

BitBucket webhook on pull request merge

thor
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 21, 2016

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.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Georgii Cherenkov
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 22, 2017

When u create new own webhook to JIRA at same URL, look into Webhook log. In JIRA (readonly) there is 

Authorization

<code>

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.

TAGS
AUG Leaders

Atlassian Community Events