Jira automation for operations
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 team 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
to automate your alert and on-call work.
Team automation
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 automationComponents 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.
Triggers
Alert created
Rule is run when an alert is created. Learn more
Manual trigger from alert
Rule is run when it is manually triggered by the user from Actions on an alert.
Alert status changed
Rule is run when an alert’s status changes.
| Status | ||||
|---|---|---|---|---|
|
Alert note added
Rule is run when a new note is added to an alert.
| Status | ||||
|---|---|---|---|---|
|
Alert updated
Rule is run when an alert’s priority, summary, or description is updated. Learn moreView all automation
| Status | ||||
|---|---|---|---|---|
|
Conditions
Alert fields condition
Checks whether an alert’s field meets a certain criteria.
Learn more View all automation about the on-call conditions
Actions
Create incident
Creates a new incident in the selected service project.
Two new rule scopes in global automation
Site admins will be able to access Global automation in Settings → System, where two new scopes have been added to support team automation.
Existing rules scopes
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
New rules scopes
Single team: Run rules only within a single team
Multiple teams: Run rules across selected teams
Need more information? Learn more about permissions required to use Jira automation
New smart values for alerts
What are smart values?
Smart values allow you to access and manipulate issue and alert data within Atlassian Cloud. They can add significant power and complexity to your rules. Learn more about using smart values in Jira
{{alert}}
{{alert.id}}
{{alert.tinyId}}
{{alert.link}}
{{alert.status}}
{{alert.message}}
{alert.count}}
{{alert.description}}
{{alert.tags}}
{{alert.priority}}
{{alert.entity}}
{{alert.alias}}
{{alert.source}}
{{alert.extraProperties}}
{{alert.owner}}
{{alert.ownerId}}
{{alert.responders}}
{{alert.responders.get(index)}} Get the responder specified in index
{{alert.responders.<property>}} Similar to other list types, prints the values of this property of each responder separated by commas. So {{alert.responders.name}} would print name1, name2, name3...
{{alert.responders.get(index).name}} Get name of the responder specified in index
{{alert.responders.get(index).type}} Get the type of responder
{{alert.responders.get(index).accountId}} Get the responder’s Atlassian account ID
{{alert.responders.get(index).teamId}} Get the Atlassian team ID of the responder type