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

Unable to "enable" automation rule

Joshua Markus

Hello,
2025-01-15 15_01_24-Rules - Automation - Jira.png

I have a power user that relies heavily on automation within her space. She has built out two automation rules (show in image above) that she is needing to enable. The second one (Group 2) is able to be enabled without a problem. However, when attempting to enable the first (Group 1), we get the following error:

We couldn't enable your rule

Check the rule's configuration and try again

The only thing that is different between to two is that there are different assignees and different statuses leveraged.

Is there any way to debug what the ACTUAL problem is rather than just getting a generic error?

Accepted answers

Neil Fletcher

Hi @Joshua Markus

I ran into something similar earlier this week.

I deleted the trigger and added it again... that did the trick.

Make a copy of the rule first and then give it a try.

All comments

Bill Sheboy

Hi @Joshua Markus

Quite recently, additional validation was added to the automation rule editor. When changing a rule, it is possible it cannot be enabled when it contains errors...but it can still be saved.

I wonder if that validation is now checking when trying to enable from the rule list. Perhaps this rule has errors that can be seen if one opens the rule in the editor and tries to enable it from there.

If that does not help, please post an image of the complete rule to provide context for the community to offer suggestions. Or, contact the Atlassian Support team to take a look: https://support.atlassian.com/contact/#/

Kind regards,
Bill

Neil Fletcher

Hi @Joshua Markus

I ran into something similar earlier this week.

I deleted the trigger and added it again... that did the trick.

Make a copy of the rule first and then give it a try.

Bill Sheboy

Hi @Neil Fletcher

Rules can get "glitched" by too many edit / publish cycles, or incompatible settings that are not resolved by the editor. Apparently something gets broken in the JSON behind the scenes, although I have not found any public backlog defects listing the symptom.

Typically the two ways to check for that are:

Disable the rule, wait a couple of minutes, re-enable it, and test. This refreshes some of the internal storage of the rule.
If the above did not work, do as you suggested: disable the current rule, re-create it from scratch, test, and if it works, delete the first one.

The other symptom I noted in my earlier post was related to the validation changes and not the existing problem with rule "glitches".

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