nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Zak Siddique

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)?

Accepted answers

Marc -Devoteam-

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.

All comments

Marc -Devoteam-

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.

Zak Siddique

Ah, I thought that might be the issue. I have read about the delayed action, but as you assumed correctly, we're still on the standard subscription.

I've made the change to < 1 - I'll post another reply if it has any significant impact.

Appreciate the answer @Marc -Devoteam-!

Bill Sheboy

Hi @Zak Siddique

Yes, and...to the suggestions offered:

The new feature to add conditions directly to triggers has racetrack timing problems (among other challenges), and so I recommend not using this feature until Atlassian improves the architecture for event-raising and rule trigger ordering.

Instead, use your rule trigger, followed by the Re-fetch Work Item Data action to add a slight delay and reload the data before the rule proceeds. Then add the conditions before your rule actions.

Kind regards,
Bill

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud