Component limit in Jira Automation rules

[Brock Jolet]

Am I wrong or did Atlassian change how they count the number of components in a single Automation rule? I noticed a while back that they add a warning at the top of rules if you near the limit of 65 components. This is definitely helpful as I have breached that limit on a few occasions.

However, I was working on a relatively simple Automation rule today and noticed that each "condition" in a single "If: any match" block counts as a separate component now. I don't think this was always the case.

For example, if I have a single block that checks if each field, "description", "due date", and "resolution" are empty, it will count as three components. If I enter it as a compound JQL query it will only count as one component even though it's doing the same thing.

Why is Atlassian constantly making the user experience worse?

[Bill Sheboy · Accepted solution]

Hi @Brock Jolet 

Short answer: yes, you are correct they count.  Here are some related suggestions to follow:

https://jira.atlassian.com/browse/AUTO-1706
https://jira.atlassian.com/browse/AUTO-1778

Just like a branch counts as one-for-count, the if / else block structure counts as one plus one for each condition... but their nested condition block components do not count.

One can review the export JSON to see the component list representation:

"components": {
  {
    "id": unique number,
    "component": "(ACTION|BRANCH|CONDITION|CONDITION_BLOCK)",
    "parentId": (null|"number"),
    "conditionParentId": (null|"id for condition parent reference to CONDITION_BLOCK id"),
    ...
    "type": "(many possible type, including jira.condition.container.block)",
    "value": {
      varies by component, type, and specific settings
    },
    "children": [child components, for branch and if-else blocks],
    "conditions": [for a CONDITION_BLOCK of an if-else, the section conditions appear here],
    ...
  },
  ...
}

(Triggers are also a possible components.component value, but are listed separately in a rule.)

And so a single if / else block has:

• a top-level CONDITION component with a type indicating if / else (i.e., jira.condition.container.block)
  • children list of CONDITION_BLOCK components, where each of those has...
    • children list with the actions, branches, conditions, etc.
    • conditions list for the conditions applying to this specific CONDITION_BLOCK
  • conditions list is empty for all other types, including the parent block itself

And so, it could be worse: they could also count the CONDITION_BLOCK components too.

Kind regards,
Bill

[Brock Jolet]

Thanks for this insight, Bill. I've voted for the suggestions as well.

[Dilip]

Hi @Brock Jolet 

The component limit in Jira Automation rules is 65 components per rule. This includes all conditions, branches, and actions, but does not count the trigger towards the limit. If you exceed this limit, you'll see an error message and will need to split your rule into multiple rules

check this article to get all the limitation deatils for automation rule - https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

[Bill Sheboy]

Hi @Dilip 

What is the source of your information regarding rule triggers as they do count toward the 65 component limit?  A rule's trigger is a type of component, and so it also counts.

You may create a test rule to verify this information.

Kind regards,
Bill