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

Performance issue in automation rule

Sundram Trivedi

I have set up an automation rule from templates where, when all child issues are completed, the parent issue is automatically closed. I followed this hierarchy: Theme → Epic → Task. When I move the Task to "Done," the Epic also mov es to "Done" after refreshing the browser. However, according to the rule, the Theme should also move to "Done" after the Epic, but it fails in automation. I had to manually set the resolution for the Epic, after which the Theme automatically moved to "Done."

Similarly, I noticed a similar issue with the In Review automation.

Additionally, the audit log does not show any information regarding these failure actions.

Accepted answers

Bill Sheboy

Hi @Sundram Trivedi

Please post an image of the audit log details for the rule execution. That may provide more context.

Next, you are trying to update multiple levels in the hierarchy with one rule, essentially having it trigger itself recursively. Did you enable the option Check to allow other rule actions to trigger this rule... in the details at the top of the rule?

Kind regards,
Bill

All comments

Tansu Akdeniz

Hi @Sundram Trivedi

Can you share a screenshot?

Does Theme automatically move to Done? Is resolution required? If so, do you set it within the rule?

Sundram Trivedi

Hi @Tansu Akdeniz ,

No, Theme automatically not move to Done, it required resolution.

Please check screenshot and let me know if anything required.

Tansu Akdeniz

You can select the Resolution within the Transition action that allows you to pass the required field.

Sundram Trivedi

But previously it was set copy from trigger issue. I changed the resolution to done then it will not work if I will select resolution any other in the ticket.

Bill Sheboy

Hi @Sundram Trivedi

Please post an image of the audit log details for the rule execution. That may provide more context.

Kind regards,
Bill

Sundram Trivedi

Hi @Bill Sheboy ,

The issue was resolved after enabling the "Check to allow other rule actions to trigger this rule" option. Should I enable this for all automation rules? Sometimes, a browser refresh is required for the changes to reflect correctly.

I have one more question:

I have set validation for Acceptance Criteria, Story Points, and Assignee in the To Do state. When I move an issue from Backlog to To Do, the validation works as expected and requires these fields to be filled. However, sometimes, after moving an issue from Backlog to To Do, the validation pop-up appears, but the issue automatically moves to In Progress or In Review instead of staying in To Do. Additionally, in some cases, refreshing the browser shows the correct state in Backlog instead. Can you help me in this.

Regards,
Sundram

Bill Sheboy

No; please do not enable that option for all rules: "Check to allow other rule actions to trigger this rule...".

By default, rules do not trigger other rules. This prevents accidental rule triggering and run-away looping / recursion. Only enable that option when you have clearly identified when a rule should be triggered by other rules. To learn more, please discuss with your Jira Site Admin.

Regarding your second question, you appear to have a validation rule on the workflow transition from "Backlog" to the "To Do" status, but do not have validation for other transitions, such as "Backlog" --> "In Progress". I recommend carefully reviewing your workflow transitions and validators to decide what is needed, and then update accordingly.

Sundram Trivedi

However, I have already set validation rules for transitions from To Do to all further states. The issue I am facing occurs intermittently—sometimes, when I move an issue from Backlog to To Do, the issue automatically transitions to In Progress or In Review without following the expected workflow.

After refreshing the browser, the issue returns to its correct state and works fine. I am sharing a screenshot for reference. Could you help identify the possible cause of this behavior?

I have set 3 workflow for our project due some different condition.

I have set validation for all states. I have noticed that this issue sometimes occurs when I create issues in the hierarchy Theme → Epic → Task.

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