How do I create an automation that when a Pull request is merged it moves the status?

Brandon Forslund March 15, 2024

Hey everyone, 

I wanna create an automation that when a pull request is merged it auto transitions the status from lets say "in progress" to "ready to test" The one that I made does not seem to be working and I am not sure if I am missing a step step with the pull request? Anyone know how to set it up?  

2 answers

0 votes
Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 15, 2024

Hi @Brandon Forslund 

Rule should look something like this:

  • Trigger: Pull request merged
  • Action: Transition Issue
    • Destination Status = Target Status here

^ Is this what your rule looks like?

This does assume the relevant developer tool (eg. Bitbucket) is connected to this Project.


0 votes
Chris Buzon
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 15, 2024

depends on the app (github, p4?) you're using for source control.  The problem is that the rules are complicated, especially if you have more than one PR on a ticket.  You have to use the development section to 'see' the PR, then in automation you tell it to move when it is successful.

There are lots of ways it goes wrong, and the 'right' (quotes intentional) solution is to use something like Github actions to send a webhook that then does the transition for you.

It will take maintenance, and your devs have to be careful. It will not automatically get fixed if you have to back out a PR or something, that's all custom work.


Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events