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 size

Don Hames

I have one more question on Jira Automation. We everyone's helpful answers, I have been able to get very far along in my project. I ran into the rule size limit. It suggested that I break my rule apart into separate rules. I have no problem with that because it will make their maintenance more manageable.

The question I have is the Best Practices for splitting a rule. Do I create a new rule triggered by the same manual trigger I am using? If so, is there an issue with ordering them or will they run simultaneously?

Or is there a way for one rule to call another rule?

Thanks again for all your help and expertise.

Accepted answers

Jack Brickey

Ho @Don Hames , I thing the answer depends on the details. However, while you cannot have a rule directly invoke another you can do so via the triggers indirectly. For example...

Rule 1 triggers on transition and sets a value in a custom field (CF)
Rule 2 triggers on issue updated with a condition on the CF value

The order that rules are triggered is top to bottom in the list. You can order them via drag and drop.

If you can share details of your rule we might be able to provide more guidance.

All comments

Jack Brickey

Ho @Don Hames , I thing the answer depends on the details. However, while you cannot have a rule directly invoke another you can do so via the triggers indirectly. For example...

Rule 1 triggers on transition and sets a value in a custom field (CF)
Rule 2 triggers on issue updated with a condition on the CF value

The order that rules are triggered is top to bottom in the list. You can order them via drag and drop.

If you can share details of your rule we might be able to provide more guidance.

Bill Sheboy

Hi @Don Hames

Yes, and...to what Jack suggests:

Some scenarios requiring longer rules can be restructured with branch loops, list iterators, conditional filters, lookup issues, smaller parent/child rules, etc. Knowing the problem you are trying to solve and seeing your complete rule may help the community to suggest alternatives.

Kind regards,
Bill

Don Hames

Thank you for your quick replies. Below is a screenshot of the rules that need to be processed from a single manual trigger. I already started breaking it apart. The pink decision symbol s the primary condition; if there are additional, they are the white decision symbols. The rectangles represent an Epic that will be created, and each Epic can have from 1 to n Stories.

My current thinking is to write each line with a pink decision symbol as a separate rule and have it trigger off the same manual trigger they all will use. Do you see any issues or have other suggestions?

rules example.png

Bill Sheboy

Don, what do the rectangles represent in your diagram? For example, is all of this logic to set the value of one field? Or is it to take additional actions?

Let's say this was to set the value of one field. In that case, much of that logic can be combined into a single conditional statement.

Would you please post an image of your rule, as you currently have it? Thanks!

Welcome!

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

Quick Links

Find more posts tagged with

server

cloud

jira-software

automation