Jira Automations

Can automation rules help smooth out some of the aspects of the testing process? Check out the suggestions below.

Jira Automation rules allow to streamline repetitive tasks and focus on what's really important. This also includes the testing process. Below, we have compiled our suggestions that could become useful in the test management system and save time of the QA teams.

Schedule Recurring Tasks

When: Recurring tasks such as regression or smoke tests.

Trigger: Scheduled (e.g., every Monday 9 AM)

Action: Clone a specific Test plan or create new Test execution work items

Inform a QA Team About a Critical Bug

Trigger: Work item created

Condition 1: Work type = Bug*

*or any other work type that has been configured as a Defect in the Testing Project

Condition 2: Priority = Critical

Condition 3: Work item has linked work items

• Link type:

• Work type:

Action:

• Slack: send message to (channel name)

Flag a Test Case For a Review After a Requirements Change

When: While making sure that the Test case is updated to the newest requirements and it covers a proper testing scope.

Trigger: Work item updated

Condition 1: Work type = Requirement

Condition 2: Work item has linked items

• Link and work types have to match the one in the Testing Project

Branch rule: For linked work items

• Link and work types have to match the one in the Testing Project

Inside branch:

• Condition: Status != Needs Review

• Action: Transition work item to Needs Review