Use cases

Synchronize parent and sub-tasks

(Only in Cloud and Server Pro versions)

Users always want to make sure sub-tasks and their parent issues are in sync. For example, when you resolve the last sub-task on an issue you want to resolve the parent. With Automation for Jira it is trivial to keep any related issues in sync.

Another common request is for sub-tasks to inherit values from their parent. E.g. fix version. It is now easy to sync these values to ensure that both parent and sub-task have up to date information.

Sync parent subtasks use-case

(Only in Cloud and Server Pro versions)

You want to make sure that when issues are closed that everyone watching related issues know that progress has been made. By iterating over linked issues you can comment on each one. Jira will then notify each watcher that the related issue has been closed.

You can perform any action on any related issue - Stories with Epics, Parent, issues previously, linked issues, or any list of issues defined by JQL.

Comment on linked issues use-case

Add sub-tasks on issue creation

(Only in Cloud and Server Pro versions)

Whether it is a formal Definition of Done or just a list of known tasks, this template allows you to quickly configure the sub-tasks when an issue is created. Service teams also love this one to enable them to define what steps must be carried out when an incident occurs.

If you only want to do this for a particular Issue Type it is trivial to add a condition that restricts it.

Create sub-tasks use-case

Auto-assign issues

(Only in Cloud and Server Pro versions)

Stories / tickets can often get lost when users forget to assign them to themselves. It is easy to do and can affect the accuracy of reporting and transparency of progress. This rule automatically assigns the issue to the user that transitions it.

You can use a condition to check for certain scenarios and assign the issue accordingly. E.g. Assign the issue to Bob when the component is "User Interface" and the status is "Testing".

Auto assign use-case

Re-open issue on customer comment

Just when you think that the ticket has been closed, the customer comes back and tells you that it is still broken...

This rule automatically puts the ticket back into the queue and lets your team deal with it. It is also pretty easy to add a notification to let the assignee know that their job isn't quite done yet!

Reopen comment use-case

Monthly recurring tasks

(Only in Cloud and Server Pro versions)

Your TPS reports are due every month, so why not use this rule to automatically create tasks to track them. With the powerful CRON schedule or the convenient periodic schedule you can customise this rule to run as frequently as your reports are due!

Monthly task use-case

Automatically respond to known errors

(Only in Cloud and Server Pro versions)

The best work is work that does itself. With this rule you can use regular expressions to check for known scenarios/errors and respond with an email that points the customer in the right direction. Your customer is happy because they receive an answer straight away and your support staff are happy since you just halved their workload.

Auto respond use-case

Send SMS for high priority issues

(Only in Cloud and Server Pro versions)

When someone raises a high priority issue, they want immediate action! This rule checks the priority of the issue and if it is Highest it will send an SMS message to the user you specify.

Customers use this rule to automate their on-call escalation process.

Send sms use-case

System field defaults

A common request for Jira is the ability to set defaults for built-in System fields. At the time of this writing there are 1075 votes for this request. Until Jira catches up, you can use Automation for Jira to set a default value for these fields on issue creation. Even better, you can use conditions to set the values based on other criteria.

System defaults use-case

Identify SLA breaches and react

Companies have SLAs for a reason and need to identify when they are breached. With this rule you can run a JQL query every hour and check what tickets have exceeded their SLA. You can then escalate, or respond to customers with an update.

SLA breach use-case