Jira project automation rules have suddenly stopped executing.

[Neil Ingram]

We have a number of automation rules setup on our Jira projects which have all been working fine but have suddenly stopped working from around 14:00 GMT today. Nothing is being added to the audit logs indicating they are not even being executed. Is the service not working? We rely on these rules so need them working again asap. Thanks

[Liam Green · Accepted solution]

Hi all

There is currently an issue with Automation that Atlassian are looking into:

https://jira-service-desk.status.atlassian.com/

Regards, Liam

[Liam Green]

Hi @Neil Ingram 

Please consider 'accepting' my answer if it has solved your query :-)

[Tanmay Sharan]

Same issue here. All my project automation rules have suddenly stopped working, with nothing in the audit logs.

[Tyler Cox]

Same issue here, our QA Sub-task creation and parent issue transitions are no longer functional

[Siri Nama]

We are facing the same issue.

[Jack Brickey]

So are you saying that there are no logs about the rule running or that the logs indicate success? Can you provide more details about these automations maybe take a screenshot of one of your automations?

[Siri Nama]

One of the examples:
I have a rule set up to send Teams message when a fix version is released. I released multiple fix versions but the rule never got executed. In fact, I have 4 rules to execute for the same action and none of them were executed. There are no entries or warnings in the audit log. We're on premium account and we have unlimited executions. So it's not that we ran out of number of executions allowed.

[Neil Ingram]

Thanks for the response. This is the rule that has suddenly stopped executing.. It simply updates the summary field when the description contains "ref:". When it stopped executing I created a very simple rule to add a comment when an issue was created and this didn't execute either.

 

[Neil Ingram]

It uses a smart value to populate the summary.

[Neil Ingram]

No logs are being written indicating its not being executed. Was working 3hrs ago.