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

Is it ok to have more than one 'Action' in single automation rule?

sowjanya gondi

I have a scenario where I need to clear a particular field based on a condition and then populate the field with a specific value after checking if it's cleared. This worked when there are few issues to be updated but when the rule was triggered on a project where the issue count was more than 100 audit log showed performance issue.

I was wondering if it might be because of 2 actions in a single rule. Should I work on optimizing this? Please shed some light here?

Thank you!

Accepted answers

Jack Brickey

I used to observe an issue with back to back creation of many tasks and sub-tasks. The automation would actually work but I would get a failure message. I spoke to Code Barrel (original vendor) and they acknowledged that there could be a false warning on such a scenario. Now, I have not seen this for a long while so I suspect it has been addressed. All that said, while it is possible, two action is not many at all. My rule had about 25 with several tasks being created and many sub-tasks. Still it is a reasonable theory that doing this on 100 issues could result in performance issues. Performance aside, is the rule succeeding? I wonder if you could somehow limit the number of issues being changed?

All comments

Jack Brickey

sowjanya gondi

The rule is succeeding in a test project where I tested. This project has tens of issues to test the rule. In an actual project it did not succeed. The only difference is the count.

But it's good to know 2 actions is not much.

"Project = TJ AND Sprint in closedSprints() AND updatedDate > startOfMonth("-6")"

That was the JQL used. 6 months of data. Since the project is new the query only retrieves about 120 issues.

sowjanya gondi

Multiple rules triggering on the Start of the Sprint for 3 different Actions should be ok too right? I am trying to split the rule with multiple actions.

JD_sjez00

Hi @sowjanya gondi , it's fine to have multiple actions on a single rule. You can have up to 65 components per rule.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

automation