Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Jira automation for operations

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

. In addition to existing scopes ( project and global automation), you now have team automation — a new automation scope where you’ll be able to create team rules to automate your alert and on-call work.

Team automation

Use automation for team operations to create rules using Alerts.

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 RulesTeam rules.

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.

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
colourPurple
titlecoming soon

Alert note added

Rule is run when a new note is added to an alert. Learn moreView all automation

Status
colourPurple
titlecoming soon

Alert updated
Rule is run when an alert’s priority, summary, or description is updated.

Status
colourPurple
titlecoming soon

Learn more about the on-call triggers

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.

Learn more View all automation about the on-call actions

Two new rule scopes in

Jira automation

global automation

Site admins will be able to access Global automation in SettingsSystem, where two new scopes have been added to support team automation.

Image Added

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.

To access global automation, you need to be a Jira admin. You’ll be able to find Global automation in SettingsSystem.

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

View all smart values available in Jira automation