Understanding service limits
Service limits for automation rules are key to ensuring that automation rules do not have a negative impact on the performance of your Jira instance.
In this section, we'll look at what service limits are in place and how they affect your rules. We'll also look at how to work within these service limits and how we can use automation rules to monitor some of these.
Let's start by looking at what service limits are available.
Getting to know service limits
Service limits are applicable to both the Jira Cloud and Jira Server/Data Center versions of the automation rules.
The service limits that apply to all rules are listed along with a description of how each limit could be breached:
- Components per rule: 65
Any rule that contains more than 65 conditions, branches, and actions.
- New sub-tasks per action: 100
A rule that attempts to create more than 100 sub-tasks.
- Issues searched: 1,000
A JQL search that returns more...
