5 Jira Automation for Agile efficiency

Deepika Goel
3 min readMar 20, 2023

--

Jira is a reasonably common software development tool used by Agile teams.

As an Engineering Manager, I am always on the lookout to improve team efficiency and processes. I recently discovered Jira automation which allows for the automation of repetitive tasks for Agile.

Jira Automation

Prerequisites

  1. Admin access for the Jira project.
  2. Manage 1 branch / pull request per issue.
  3. Use the issue key in the branch name or a commit message
  4. The issues have statuses in a workflow including — To Do, In Progress, In Code Review, Ready for QA, and Done.

Where to access Jira Automation?

  1. On the Jira Project left pane; select “Project Settings”.
  2. On the “Project Settings” left panel; select “Automation”.

Jira Automation

1. Update an issue status to In Progress or Code Review

Additional Prerequisites

N/A

Automation

When a branch for an issue is created and the issue status is not “In Progress”, the status will be updated to “ In Progress”. Similarly, when a pull request for an issue is created, the issue status will be updated to “In Code Review”.

Jira Automation — Move to In Progress and Move to In Code Review

2. Assign an issue to a QA engineer upon merge of a pull request

Additional Prerequisites

  1. Each issue has a “QA Assignee” field and during Sprint grooming a QA engineer is assigned.
  2. Continuous Deployment is set up for lower environments upon merge.

Automation

When a pull request is merged, the issue will be re-assigned to “QA Assignee” and the status of the ticket will be updated to “Ready for QA”.

Visual representation of Move to Ready for QA and Set Assignee as QA Assignee
Visual representation of Edit Issue Set Assignee as QA Assignee in JIRA
Jira Automation — Assign an issue to a QA engineer upon merge of a pull request

3. Update the due date for an issue based on the sprint’s last day

Additional Prerequisites

N/A

Automation

When a ticket is moved into a sprint or in a future sprint, the “Due Date” will be updated to the last day of the sprint.

Jira Automation — Update the due date for the issue based on the sprint's last day

4. When the first issue is in progress then update the epic to “In Progress”

Additional Prerequisites

N/A

Automation

When an issue under an epic is moved to “In Progress” and the epic is not already in progress, the status of the epic will be updated to “In Progress” as well.

Visual representation of When the first story is in progress → then update the epic in progress in JIRA
Jira Automation — When the first issue is in progress then update the epic to “In Progress”

5. When all the issues are completed then update the epic to “Done”

Additional Prerequisites

N/A

Automation

When all issues under an Epic are moved to “Done”, the status of the epic will be updated to “Done” as well.

Visual representation of when all stories are completed then close epic in JIRA
Jira Automation — When all the issues are completed then update the epic to “Done”

Summary

You can use Jira automation to increase agile efficiency by manually re-assigning issues, updating statuses, and managing timelines and communication.

--

--

Deepika Goel

Engineering Leader, feminist, all kinds of testing fanatic