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

Managing the scope of a sprint

During any development life cycle, it is inevitable that at some point there will be a change to the scope of the sprint, either due to last-minute changes to the requirements or by the need to include an urgent bug fix.

In this section, we'll firstly look at how we can change the scope of a sprint by including a newly linked issue to the sprint.

We'll also look at how we can use automation rules to monitor the sprint and notify the team when the scope changes.

Creating a rule to add a linked issue to the sprint

In this example, we are going to make use of the fact that we have both a private internal software development project (My Application with key MAPP) and a public support project (My Application Support with key MAPS) where customers can raise requests and report bugs.

We are also going to assume that we have a team that monitors the public support project and triages incoming requests.

Part of this triage involves...