Automation

Jira automation now includes new components for on-call teams to automate operations tasks and processes.

In addition to existing automation scopes (project and global automation), you can now have team rules — a new automation scope where you’ll be able to create rules using alert triggers, conditions, and actions.

Scopes in Automation

Here’s a quick overview of what each scope in Automation offers:

Projects

Use automation in service projects to create rules using,

• Service requests

• Incidents

• Problems

• Changes

• Post-incident reviews

… and other Jira issue types.

If you’re a project admin, you’ll be able to find Automation in project settings. Pick a template to get started or view the rules of your service project by selecting Rules → Team rules.

On-call teams

Use automation for team operations to create rules using,

• Alerts

• On-call work

If you’re a team admin, you’ll be able to find Automation on the team’s Operations page. Pick a template to get started or view the rules of your team by selecting Rules → Team rules.

Global automation

Use global automation to create and run rules in any scope:

• Global: Run rules globally

• Single project: Run rules only within a single project

• Multiple projects: Run rules across selected projects

• Project type: Run rules across all projects of a specified type

• Single team: Run rules only within a single team

• Multiple teams: Run rules across selected teams.

If you’re a Jira admin, you’ll be able to find Global automation in Settings → System on your Jira site.

Need more information? Learn more about permissions required to use Jira automation

Components for on-call team rules

We’ve added 3 new components as of yet to help you create incidents based on your alerts. You can use these components with already available components across project and global automation.