You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am using Jira Automation to automatically move a ticket to a certain state (Code review Completed) when a PR is approved in BitBucket. I have generated a webhook in BitBucket with PR Approved as a trigger. This hook is then used in Jira Automation to move the issue to Code Review Completed state. However, when the PR approved event is triggered, no Issues object is getting passed from the hook and hence Jira Automation is throwing an error - "No issues from the webhook". Can someone help?
Hello @Joy Paul ,
Welcome to Atlassian Community!
I'm afraid that currently, the Pull Request:Approved webhook JSON payload does not contain a specific issues object to be interpreted by the Jira automation. The issue key is only returned in the title of the PR, in case was included there, but Jira won't really look for that field.
I went ahead and created a feature request to include the issues object on the Pull Request webhook payload, which you can find in the following link :
I would suggest you to add your vote there, since this helps both developers and product managers to understand the interest. Also, make sure you add yourself as a watcher in case you want to receive first-hand updates from that ticket. Please note that all features are implemented with this policy in mind.
While this feature is not implemented, we have Automations developed for other Pull Request events, such as Created, Merged or Declined. These can be found directly in the Jira automation page and do not require you to manually configure a bitbucket webhook :
Hope that helps!
Thank you, @Joy Paul !
Hey @Patrik S , I can suggest a different approach as I am also facing this exact issue.
You can bring up another web service as "middleware" between the Bitbucket trigger and JIRA automation. For example some simple flask server.
In this middleware API (that you triggered from the pull request event) you can process the body of the request into a format that JIRA automation can handle and send it to the the automation rule to trigger a status change for the issue (or any other action supported there).
Hope this helps!