Book Image

Automate Everyday Tasks in Jira

By : Gareth Cantrell
Book Image

Automate Everyday Tasks in Jira

By: Gareth Cantrell

Overview of this book

Atlassian Jira makes it easier to track the progress of your projects, but it can lead to repetitive and time-consuming tasks for teams. No-code automation will enable you to increase productivity by automating these tasks. Automate Everyday Tasks in Jira provides a hands-on approach to implementation and associated methodologies that will have you up and running and productive in no time. You will start by learning how automation in Jira works, along with discovering best practices for writing automation rules. Then you’ll be introduced to the building blocks of automation, including triggers, conditions, and actions, before moving on to advanced rule-related techniques. After you’ve become familiar with the techniques, you’ll find out how to integrate with external tools, such as GitHub, Slack, and Microsoft Teams, all without writing a single line of code. Toward the end, you’ll also be able to employ advanced rules to create custom notifications and integrate with external systems. By the end of this Jira book, you’ll have gained a thorough understanding of automation rules and learned how to use them to automate everyday tasks in Jira without using any code.
Table of Contents (16 chapters)
1
Section 1: Getting Started – the Basics
4
Section 2: Beyond the Basics
8
Section 3: Advanced Use Cases with Automation

Ensuring epics and stories are aligned

Working in software projects using the Scrum Agile framework generally involves having a hierarchy of issue types.

In a typical Scrum-based agile hierarchy, you will have epics that define larger pieces of work, or business requirements, which may span multiple sprints.

These are broken down into stories (or user stories), which are high-level definitions of the requirements that can be delivered in a time-boxed period or sprint.

Stories can then be decomposed into tasks, modeled as sub-tasks of the story, which are specific, measurable items of work required to get the story done.

In this section, we'll look at how we can use automation rules to keep the statuses of the issues in this hierarchy in sync so that when work is started on a sub-task, the linked issues above the sub-task move to the correct status without needing manual intervention.

Creating a rule to keep epics and stories synchronized

In this example, we...