Forums

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

What's going wrong with my Code Review to Testing automation?

Zak Siddique September 11, 2025

I have an automation that is meant to transition stories from 'Code Review' to 'Testing' when all pull requests are merged. They pull request status is linked through the Jira <> Github integration.

 

This is my implementation:

Trigger: Pull request merged
Conditions: `development[pullrequests].open = 0 & Status = Code Reveiw`

Action: Transition work item to Testing

Screenshot 2025-09-11 at 10.32.02.png

 

Intended behaviour:

If my story has 3 pull requests open, when the first 2 are merged, the story status does not change. When the final one is merged, the story should change to Testing

 

For some reason, the automation runs correctly in some instances but then doesn't run correctly in others, and I'm struggling to find a pattern or a known reason why this might be.

Am I missing something? Is there a better way of achieving the outcome I'm looking for?

Could it be due to delays in the integration and running of the Jira automation (Github <> Jira <> Jira Automations)?

 

1 answer

0 votes
Marc - Devoteam
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.
September 11, 2025

Hi @Zak Siddique 

Delays between the apps can definitely be the issue here.

On a premium subscription you can add a delay action in your automation, but based on your tags on the question you are on a standard subscription.

You could try to adjust the condition to not to use = 0 but < 1, it might help.

But still I think you could have erratic behaviour.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events