Automation basics
Understand the general concepts and best practices of automation in Atlassian cloud products.
In Jira Cloud, some project templates come with automation rules already set up - these are called system rules. When system rules run, they don’t count towards your usage.
System rules are only created upon project creation - you can’t convert a regular rule into a system rule, or vice-versa.
There are currently no system rules in Confluence.
Product | Project template | System rules |
---|---|---|
Jira Service Management | IT service management |
|
| Customer service management |
|
| IT service management (Essentials) |
|
System rules can’t be modified: The components within a system rule can be edited, but you can’t add or remove any components. To modify the behaviour of a system rule, you’ll need to disable the rule, make a copy of it, and modify the new rule instead. However, if you do this, the new rule that you create will count towards your usage every time it runs.
System rules will always be created with a project: If a project template includes system rules, then those rules will always be created when the project is created - this will be true, even if you stop project admins from creating automation rules.
Was this helpful?