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

Understanding service limits

Service limits for automation rules are key to ensuring that automation rules do not have a negative impact on the performance of your Jira instance.

In this section, we'll look at what service limits are in place and how they affect your rules. We'll also look at how to work within these service limits and how we can use automation rules to monitor some of these.

Let's start by looking at what service limits are available.

Getting to know service limits

Service limits are applicable to both the Jira Cloud and Jira Server/Data Center versions of the automation rules.

The service limits that apply to all rules are listed along with a description of how each limit could be breached:

  • Components per rule: 65

    Any rule that contains more than 65 conditions, branches, and actions.

  • New sub-tasks per action: 100

    A rule that attempts to create more than 100 sub-tasks.

  • Issues searched: 1,000

    A JQL search that returns more...