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

Using a checklist

When you are creating your rules, you are not always going to remember all the various points we have discussed in this chapter to ensure that your rules follow best practices.

Having a checklist that you can quickly reference can help in ensuring that you have followed both the best practices we have presented in this chapter and any organizational guidance you have prepared.

We have, therefore, put together a basic checklist that you can use as a starting point to create a checklist in the format that suits you best:

  • The rule is correctly scoped to only the project or projects that are affected.
  • The rule is documented and includes a business case and implementation approach.
  • The rule has been exported and stored in a version control system such as GitHub or Bitbucket.
  • An appropriate trigger was used, such as Field value changed rather than Issue updated.
  • The rule is using the most efficient conditions, such as the Issue fields condition...