5 New Ways Testers Can Leverage Automation in Jira Cloud

Insight Main Image

Atlassian has recently announced that the powerful automation engine has become a native feature for all Jira Cloud instances! 

This automation in Jira provides a no-code solution to automate tasks that occur in the day-to-day management of work in Jira.  

To get started with automation in Jira, task creation can be done either at the global Jira level or for a single project. In these examples, we created these automation rules under a single project so to start we went to Project Settings > Project Automation. 

Automation rules in Jira work on a simple system that starts with a Trigger, any number of Conditions to narrow the scope of the trigger, which leads to a set of Actions.  

In this article, we will cover five ways that testing teams can leverage this new update to automate tasks during test management activities. These examples will use the “Test” Issue type provided by Zephyr for Jira

Sprint Notifications d4a54864e16a853c00fd6b56c71ff1c1.png

As software release work continues in Jira, teams can leverage Scrum boards to manage all activities including testing managed by Zephyr. Every time a new sprint starts or ends, we can communicate this instantly through email, slack, hipchat, stride, and Microsoft teams. 

In this example, the Trigger is when a sprint starts on my “Smart Scrum” board then the Action will notify my testing team via a specific slack channel that they monitor.  

Test Change Notifications  74b632e078adadc85e9c4a3391ac9a90.png

With the extensive integrations offered into communication tools, we can use automation rules to notify testers when a Zephyr “Test” is changed in any way.  

Tests created by Zephyr for Jira can be linked to other issue types in Jira like “Story” which can describe functionality important to the software release. Project Managers may come into Jira during a grooming session and update links from newly created “Story” issues to related Zephyr “Test” issues. Instead of testers constantly monitoring these tests manually for any new stories linked, you can create an automation rule to notify them via Slack.  

In this case, the Trigger will be set as “Issue Linked” with the type “Relates”. Since we are focusing on tests, we will leverage the Condition “If: Issue Type equals” with the value “Test” which is the Zephyr for Jira issue type. The Action will be “Send Slack Message” to the testers slack channel. This message will tell the assignee specifically that a new story has been linked to a specific test (including its ID). 

Test Issue Type Assignment Based on Component 

3d455f581aea18ba1962455a43bf90ac.pngAs QA managers create more Zephyr tests in Jira, they can link that test to a Component in Jira to signify what area of the software is being tested. Each test created for a component can have a specific tester assigned to it since they are considered an expert in that area of the software.  

Automation in Jira can create rules triggered when an Issue is created. We can utilize two conditions that narrow the scope to Zephyr “Test” issue types and a list of Components that are being targeted. Based on those components, the Action can assign that “Test” issue to a specific tester.  

Synchronize Tests and Requirements 

0d57f276156163b33a543219d162a500.pngIn Jira, requirements for software releases can be linked to Zephyr “Test” issues. This is crucial to provide full end-to-end visibility in how testing work impacts the software release.  

As these issues are created, it is difficult to ensure that aspects like the Priority is synchronized to ensure high priority is reflected from requirement to its tests.  

For this example, we will automate the task of ensuring the priority of tests are the same as their related requirement (indicated by the “Story” issue type). In this automation rule, the Trigger is “When: Value changes for Priority” with the Conditions set as “If: Issue Type equals Story” and “Linked Issues match type= ‘Test’ “. Here we will introduce a Branch rule “For Linked Issues Types” to focus on just the linked test issues. The Action “Edit Issue” will copy the Priority from the story issue (which is the trigger issue) and change the test issue.  

Add important test activity to audit log 

This last automation rule is focused on automating critical updates to the Jira audit log. Automation in Jira includes a Trigger “Add Value to Audit Log”. Once an organization defines what dictates a critical testing activity, rules can be created to automatically update the log.  

In this example, we make sure to log every time the due date of a test is modified. The Trigger is “When value is changed: Due Date” with the Condition “If: Issue Type equals Test”. As a result, the audit log is updated with this change including who made it.  

These five automation rules are just the start. Automation in Jira can be combined with test management for various repetitive tasks.  

Zephyr for Jira is the most trusted test management add-on that enhances Jira with focused test management, the ability to analyze quality metrics with a variety of test metric gadgets, and most flexible integrations with BDD and test automation. 

Explore the integration between Automation in Jira and Zephyr for Jira today! 

Start a 30-day free trial