How Jira Automation Supercharges Your Workflow Without Writing Code

Feature Overview

In the first half of 2020 Atlassian launched Jira Automation on Jira Cloud, bringing powerful no‑code automation directly into the native product without extra plugins. It helps teams automate repetitive tasks, standardize multi‑team processes, integrate IM tools, and support DevOps practices.

Management Page and Entry

The management UI is simple. Rules are categorized by type (All, Global, Project) and can be filtered with custom tags. Each rule shows name, owner, project, and an enable switch, and supports copy, move, and export.

There are two entry points:

From a project's side‑bar under "Jira Automation" showing rules belonging to that project and owned by the current user.

From the System settings side‑bar (requires admin rights) showing all rules.

The top‑right corner provides a "Create rule" button and a "Performance insight" menu to view execution count, total time, average time, and results.

The page also offers an Audit Log and a Library of rule templates.

Rule Creation

When creating a rule you define its details and process. You can set the rule scope (single or multiple projects), allow other rules to trigger it, configure error notifications, assign an owner, and specify the executor.

Process Definition

Jira Automation abstracts a rule into four component types:

Trigger component (trigger)

Condition component (condition)

Action component (action)

Branch component (branch)

Trigger (trigger)

Triggers are the rule’s input. Four trigger categories are provided:

Issue trigger – reacts to changes in projects, sprints, versions, or issues.

DevOps trigger – fires on code, branch, build, or release events after integrating with external tools.

Integrations trigger – generates a webhook URL; incoming webhooks can pass an issue key, JQL query, or empty payload.

Scheduled trigger – runs at a specific time or interval, supporting CRON expressions.

Condition (condition)

Conditions evaluate whether the rule should continue after a trigger fires. Common conditions include:

Advanced compare condition – compares two values with operators like equals, contains, greater‑than, or regex.

If / else block – basic if‑else logic, with optional nested conditions.

Issue fields condition – checks issue fields against values, supporting comparisons with related issues.

JQL condition – filters issues using JQL, enhanced with smart values.

Action (action)

Actions perform the actual work. Main groups are:

Issue actions – create, update, transition, or delete issues.

Notifications – send email or web request (the latter can include custom headers, body, and store the response in a smart value).

Jira Service Management – service‑desk operations (not covered here).

Software – version operations such as create, release, or un‑release.

Advanced – special capabilities like

Lookup issues

and

Create variable

for smart values.

Branch (branch)

Branch components let you isolate a subset of issue data for separate processing, preventing interference with other rule parts.

Advanced branching – handle a specific smart‑value object and give it an alias.

Branch rule / related issues – filter related issues for further actions.

Smart Values

Smart values let you access and manipulate almost any Jira data inside automation, including issues, changelogs, commits, users, sprints, versions, and custom data like

lookupIssue

or

webhookResponse

. Examples:

<code>- Return the description field of an issue: {{issue.description}}</code>

<code>- Return the issue key: {{issue.key}}</code>

<code>- Return the current status: {{issue.status}}</code>

List operations, string manipulation, and JSON/URL encoding are also supported.

<code>- Average story points of subtasks: {{issue.subtasks.Story Points.average}}</code>

<code>- Join fix version names with " - ": {{issue.fixVersions.name.join(" - ")}}</code>

<code>- Regex match on summary: {{issue.summary.match(".*(lo).*")}}</code>

Practical Cases

Jira & Confluence Backup

Before Automation, backups required manual steps or external scripts. Using a Scheduled trigger (CRON) on Wednesdays at 12:00 UTC, two actions are defined: a web request to call the backup API and an audit‑log entry that stores the response via

{{webhookResponse}}

.

Auto‑create Sub‑tasks When an Epic Is Created

A rule with an "Issue created" trigger filters for Issue Type = Epic, then uses a Create issue action to generate predefined sub‑tasks. The Epic Link is set to

{{triggerIssue}}

and the sub‑task summary includes

{{triggerIssue}}

to identify its parent.

Sync Development Release Versions to Implementation Project

A Version released trigger (filtered by project key via regex) records the version name in the audit log, then a condition checks

{{version.project.key}}

against allowed projects (PI, HZPI). Subsequent actions create or release the version in the target project.

Sync Fixed Bugs of a Release to an IM Group

Using the same Version released trigger, a Lookup issues action fetches bugs fixed in that version via JQL. The resulting

{{lookupIssues}}

is formatted into a JSON payload (shown below) and sent via a web request to the IM service, allowing multiple bugs to be posted in a single message.

<code>{
  "msg_type": "post",
  "content": {
    "post": {
      "zh_cn": {
        "title": "{{version.name}} 发布，修复 bug 清单",
        "content": [
          {{#lookupIssues}}{{^last}}[{"tag":"a","href":"{{url}}","text":"{{key}}"},{"tag":"text","text":"：{{summary}}"},{"tag":"text","text":" @{{reporter.displayName}}"}],{{/}}{{/}}
          {{#lookupIssues}}{{#last}}[{"tag":"a","href":"{{url}}","text":"{{key}}"},{"tag":"text","text":"：{{summary}}"},{"tag":"text","text":" @{{reporter.displayName}}"}]{{/}}{{/}}
        ]
      }
    }
  }
}
</code>

Summary

Jira Automation is a simple yet powerful no‑code tool that lets teams replace repetitive manual work with drag‑and‑drop rule components, dramatically lowering the barrier to automation. Its design philosophy and abstraction logic are also valuable references for building similar automation platforms.

References

Jira Automation Cloud official documentation: https://support.atlassian.com/jira-software-cloud/docs/automate-your-jira-cloud-processes-and-workflows/

Smart‑values Cloud official documentation: https://support.atlassian.com/jira-software-cloud/docs/what-are-smart-values/