Sync Jira with your git provider

Step 1: Choose your trigger

Every rule starts with a trigger. In this case, it will be the ‘Pull request merged’ trigger. Whether you use Bitbucket or a third party tool like GitHub or GitLab - you will need to link the accounts first. Learn how to do that here. You only have to do this setup once, the first time you create a DevOps rule.

Step 2: Add your condition

A condition refines the rule so it won’t act too broadly. Here, we add the ‘Issue fields’ condition, specifying that status is ‘In Review’

Step 3: Add JQL condition

Now, we add another condition. The Issue fields condition is easier to use but the JQL condition can get much more granular. This time we are going to choose the JQL condition to do just that.

We use JQL here to tell automation to ensure there are no open pull requests still to do. The JQL for this in our case is development[pullrequests].open = 0

Step 4: Add ‘Transition issue’ action

The action we want to choose here is to transition the issue to ‘Done’.

Step 5: Add another action

You can add multiple actions. In this case, we simply want to add a value to the audit log as we might want to use this in a later rule. Here we use a smart value: {{issue.key}} has been merged.

Step 6: Test it!

It is best to test rules like this out on a free personal instance of Jira first or in a sandbox to ensure everything is running smoothly. As ever, follow the audit log for breadcrumbs of all activity.