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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
Is there a similar Jira automation rule to transition issues during a PR merge as the one in the link below, but using Bitbucket Data Center instead of GitLab?
https://www.atlassian.com/devops/automation-tutorials/jira-automation-rule-on-pullrequest-merge
Hi @Leelina Dagim,
Welcome to Atlassian Community!
Yes, there is an option on Data Center to do this using workflow triggers. Workflow triggers allows you to transition an issue when the pull request is merged in Bitbucket, and there also other triggers that can be used based on Bitbucket events.
If you want to use automation my guess it that that is possible too, you just have to add automation to your instance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your response, Mikael! Is there away for Bitbucket to notify Jira when pull requests are merged and include the build number in the Jira ticket?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, the development information does show build status according to this KB.
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.