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

Synchronizing deployments with sprint completion

In Agile scrum, one of the artifacts created during a sprint is the Product increment, which is the deliverable produced by completion of the product backlog tasks during a sprint. In this section, we'll learn how to integrate with Jenkins using automation rules to automatically initiate the final deployment build when the sprint in Jira is closed.

During a sprint, in a trunk-based development model, developers will commit code to the branch in the source repository associated with the development task, which will generally initiate automated tests to verify that the new code does not negatively affect the build process. When pull requests are created and merged, further automated tests can be initiated followed by automated deployments to QA or staging servers. By the time the sprint is completed, all these processes result in the final task of deploying the resultant product increment to production, or by using a tool such...