Maximum number of 65 Components in Jira Cloud Automation
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
According to Automation service limits, you can't exceed 65 components per automation rule, otherwise, you will see the following error message while trying to save or enable the rule:
⚠️You've reached the maximum number of 65 components allowed per rule. Please consider splitting this automation rule into multiple rules.
You might see this error message even if the Automation Rule Editor shows fewer than 65 components. This article provides additional detail and context about what happens behind the scenes.
Solution
Understand the number of components in a rule
As the automation trigger doesn't count towards the 65-component limit. Let's suppose your automation rule has the following component structure:
WHEN: Issue created
IF: all match
Reporter is in administrators
Summary contains Component count
Priority is one of: Highest, High
THEN: Assign the issue to X
When checking the Automation rule as shown above, you would assume it has only two components (IF and THEN). However, if you export this automation rule into a JSON file and inspect its components, you'll find it has more components:
"components": [
{
"id": "328153139",
"component": "CONDITION",
"parentId": null,
"conditionParentId": null,
"schemaVersion": 1,
"type": "jira.condition.container.block",
"value": null,
"children": [
{
"id": "328153140",
"component": "CONDITION_BLOCK",
"parentId": "328153139",
"conditionParentId": null,
"schemaVersion": 1,
"type": "jira.condition.if.block",
"value": {
"conditionMatchType": "ALL"
},
"children": [
{
"id": "328153144",
"component": "ACTION",
"parentId": "328153140",
"conditionParentId": null,
"schemaVersion": 3,
"type": "jira.issue.assign",
"value": {
"assignType": "SPECIFY_USER",
"smartValue": null,
"itsmOpsOncall": null,
"jql": null,
"issueToCopy": null,
"fieldToCopy": null,
"listAssignMethod": null,
"assignee": {
"type": "CLEAR",
"value": "clear"
},
"restrictedToGroup": null,
"group": null,
"role": null,
"excludedUsers": [],
"userList": []
},
"children": [],
"conditions": [],
"connectionId": null
}
],
"conditions": [
{
"id": "328153141",
"component": "CONDITION",
"parentId": null,
"conditionParentId": "328153140",
"schemaVersion": 4,
"type": "jira.user.condition",
"value": {
"conditions": [
{
"field": "reporter",
"check": "IN_GROUP",
"criteria": [
{
"type": "ID",
"value": "administrators"
}
]
}
],
"operator": "OR"
},
"children": [],
"conditions": [],
"connectionId": null
},
{
"id": "328153142",
"component": "CONDITION",
"parentId": null,
"conditionParentId": "328153140",
"schemaVersion": 3,
"type": "jira.issue.condition",
"value": {
"selectedField": {
"type": "ID",
"value": "summary"
},
"selectedFieldType": "summary",
"comparison": "CONTAINS",
"compareValue": {
"type": "VALUE",
"modifier": null,
"value": "Component count",
"multiValue": false,
"source": null
}
},
"children": [],
"conditions": [],
"connectionId": null
},
{
"id": "328153143",
"component": "CONDITION",
"parentId": null,
"conditionParentId": "328153140",
"schemaVersion": 3,
"type": "jira.issue.condition",
"value": {
"selectedField": {
"type": "ID",
"value": "priority"
},
"selectedFieldType": "priority",
"comparison": "ONE_OF",
"compareValue": {
"type": "ID",
"modifier": null,
"value": "[\"1\",\"2\"]",
"multiValue": true,
"source": null
}
},
"children": [],
"conditions": [],
"connectionId": null
}
],
"connectionId": null
}
],
"conditions": [],
"connectionId": null
}
],In the JSON output, there are actually six components, and some of them will also count toward the 65-component limit. When you exceed the 65 components in the JSON file, you should receive the respective error message.
Workaround
The current workaround is splitting your single automation rule components among different automation rules so you don't exceed their limits.
There is a feature request to increase this limit:
Was this helpful?