Automation in Jira tutorials

Automatically transition the parent issue

(If there are no additional unresolved sub-tasks)

1. Use the Issue transitioned trigger. This trigger lets your rule run when an issue transitions from one status to another. Set the trigger to respond when an issue is transitioned to Done.
2. Add an Issue fields condition to your rule that checks if the issue type is a sub-task. If the issue that triggered the rule is not a sub-task, then the rule will stop running.
3. Branch the rule, selecting parent as the related issue type. This will mean that subsequent conditions and actions will be performed on the parent issue of the issue that triggered the rule.
4. Add a Related issues condition to your rule to check if sub-tasks match status = done. This will ensure that all sub-tasks of the parent issue are Done.
5. Finally, set and configure the Transition issue action, so that the status of the parent issue is changed to Done.
6. Give your rule a name, and turn it on.

Find additional rules in the automation template library.

Enable sub-tasks to inherit values from their parent

Use the Field value changed trigger. This trigger lets your rule run when the value of a selected field changes. Set the trigger to monitor the Fix versions field.

1. Branch the rule, selecting sub-task as the related issue type. This will mean that subsequent conditions and actions will be performed on any sub-tasks of the issue that triggered the rule.
2. Set and configure the Edit issue action to set the Fix versions field by copying the value from the parent issue.
3. Give your rule a name, and turn it on.

Find additional rules in the automation template library.

Auto-assign issues to your team

How does your team handle unassigned issues? Often teams leave this to the discretion of their engineers, which can result in some unassigned issues slipping between the cracks.

1. Select a trigger for your rule, and any conditions you want to configure to define the issues that you want to auto-assign.
2. Use the Assign issue action. This action allows you to easily assign issues for a number of different scenarios.
3. Set the action to assign the issue to a user in a defined list. This will allow you to specify a series of users from which the action will select the assignee from.
4. Set the method to choose the assignee as balanced workload. This means that the issue will be assigned to the user with the least amount of open issues assigned to them.
5. In the user list, search for and select the members of your team.
6. Select Save to apply the action, then give your rule a name, and select Turn it on.

Automatically scheduling tasks can not only reduce manual work for your team, but also ensures consistency and reliability in your workflow. For example, if a customer hasn’t responded to your support engineer’s query on an issue, you can configure a rule to automatically send them a reminder and temporarily close the stale issue.

1. Use the Scheduled trigger. Set the appropriate time and cadence for the rules by using the dropdown filters.
2. Add a Comment on issue action, informing the customer that the issue has been automatically closed due to inactivity.
3. Set and configure the Transition issue action, so that the status of issue is changed to Resolved.
4. Give your rule a name, and turn it on.

Find additional rules in the automation template library.

Automation integrates with your source code management tool to allow you to automate your development processes.

1. Use the Pull request merged trigger. This trigger lets your rule run when a pull request is merged in your repository.
2. Add the If/else block condition. This condition allows you to perform alternate actions based on whether your conditions match or not.
3. On the If block, add and configure the Related issues condition to check if linked issues with the link type feature flagged by are present.
4. Set and configure the Transition issue action, so that the status of issue is changed to Rolling out. 
5. On the Else block, set and configure the Transition issue action, so that the status of issue is changed to Done.
6. Give your rule a name, and turn it on.

Find additional rules in the automation template library.

1. Use the Commit created trigger. This trigger lets your rule run when a commit is created in your source code management tool.
2. Add and configure the User condition to check if the assignee is either John or Nicole.
3. Set and configure the Send Slack message action, so that a message is sent to your team’s channel informing of the commit.
4. Give your rule a name, and turn it on.

Find additional rules in the automation template library.