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; } } }

Jira Automation Rule stopped running after few successful runs

Amulya Sankara

Hi,

I created a Jira Automation rule for a company-managed project which states that all issues with status NOT EQUAL to DONE should be moved to next sprint when the current sprint is closed. I had to add an automation rule for this since I have multiple statuses in the Done category.

This rule has been validated without errors but it did not execute when I closed the Sprint. I then created the same automation rule in a Test Project. And the rule executed successfully when I closed the sprint. I tried it a few times in the Test Project and it worked fine.

Today I executed this again and the rule did not work, even in the Test Project. In the Audit Log, it does not show that the rule was executed. I can only see the previous successful runs.

Has anyone faced this? And how can I troubleshoot this?

Thanks!

Accepted answers

All comments

Marc -Devoteam-

Hi @Amulya Sankara

You rule mentions that the sprint has to be closed in a specific board.

Why don't set the trigger on sprint completed, without setting a board. the rule will then run on each sprint closed on any board.

Vishal Biyani_2pr07j

@Amulya Sankara

Can you check if you are hitting the automation limits and hence the rule is not executing?

Automation service limits | Cloud automation Cloud | Atlassian Support

Amulya Sankara

Hi,

I have checked this and we have a lot of space left in the automation limits.

Amulya Sankara

Hi,

When I select the condition of sprint completed, it is required to select the project board. It doesn't seem like this is a board related issue.

Vishal Biyani_2pr07j

@Amulya Sankara

Can you check and confirm if the scope of automation is project level or global?

Bill Sheboy

Hi @Amulya Sankara

When did you first notice this symptom of the rule not running?

There is an Atlassian production incident today where rules are delayed / not running when expected. Please look here to follow progress on it:

https://jira-software.status.atlassian.com/

Kind regards,
Bill

Amulya Sankara

It is in project level

Amulya Sankara

Hi,

I did some tests and it does work sometimes and other times it gives me an error. Based on my analysis, it might be a timing issue and looks like sometimes the execution is delayed and so it doesn't find some steps in the rule during the delay.

I noticed it about 15 days ago for the first time. And investigated last week but it seemed to be working fine. I am facing the issue again today.

I am not sure if it's the Atlassian incident you shared, but this definitely seems like a likely cause.

Thanks for sharing! I will keep an eye on this.

Andrew Barnard

We have been experiencing this for the past week or so too.

We have rules to re-open jobs when a comment is added but the comment is being added, the job closed and then a few hours later it is getting re-opened like the automation has only just realised there was a comment.

Our rules are at Global level.

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

jira-automation