Conditions

Issue Fields Condition

  • Use smart values here: No
  • Available in Server Lite: No

This condition allows you to quickly put a condition together without needing to write smart values or JQL. You just click what you want from our populated dropdowns and fill in the blanks. It supports most common Jira fields. Use this condition ahead of JQL and Compare condition, where possible.

Reopen an issue if the reporter comments

Compare

  • Use smart values here: Yes
  • Available in Server Lite: No

This powerful condition allows you to compare objects using using smart values and regular expressions. This is best used when you want an action to only occur when a specific condition is met (for example, if the comment author matches the reporter.)

Let's look a real life use case as per the screenshot below. If you wanted to re-open a Jira issue when a customer comments, you would start with the Issue Commented trigger, add a condition that compares the comment's author with who the reporter is, add lastly add another condition to check if the issue's status is 'Done.' Once these conditions are satisfied, transition the issue to 'In Progress'

Reopen an issue if the reporter comments

Comparison Methods:

  • Equals (the assignee is Bob)
  • Does not equal (the assignee is not Bob)
  • Starts with (the reporters name starts with A)
  • Contains (the summary contains Beer)
  • Does not contain (the summary does not contain Beer)

Comparing using regular expressions

You can use regular expressions to test for a pattern. For example, check whether a field value contains, exactly matches or doesn't contain what is in the regular expression field:

Match multi-values

If/Else block

  • Use smart values here: Yes
  • Available in Server Lite: No

The 'If else' block allows for alternate actions to be executed based on whether certain conditions match or don't match. It is a really powerful condition and you can add as many if/else conditions as you want. Read more about it in this blog.

Else if solution

Issue attachments

  • Use smart values here: No
  • Available in Server Lite: No

This condition runs a simple check: does the comment or description field have any attachments? For example, you may want to check whether a customer has included a screenshot, a vendor has included an invoice, or your lawyer has attached your divorce papers.

Issue attachments condition

When an issue is created, if there are no attachments, then you can leave an automated comment for the customer requesting more info.

Issue attachments condition

To get more granular, you could combine this condition with a JQL search condition to see if the filename is a specific format. You can also include a conditional compare on some of the properties of your attachments (list not exhaustive):

JQL

  • Use smart values here: No
  • Available in Server Lite: Yes

This condition checks to see if the issue matches the specified JQL. If it does, the rule runs. For example, to assign support issues based on the content of the summary field, add a JQL search to look for specific words. If the issue has them, then assign the issue accordingly.

Auto Assign Issues

There is lots of information on how you can use JQL to search for issues from Atlassian.

  • Use smart values here: No
  • Available in Server Lite: No

This condition goes through issues that are linked to the trigger issue (parent, sub-tasks, epics, stories, etc.) and checks if the related issue exists, does not exist, or if it matches a JQL query or not.

Related issues condition

User

  • Use smart values here: Yes (use in Criteria)
  • Available in Server Lite: Yes

This condition allows you to check whether a specified user exists or is in a specified group. You can add multiple criteria for checking users in a single condition and you have the option to match all of them or just some of them.

So if you want to check if the user who added a comment to an issue was the reporter of the issue OR is a member of the ‘participants’ custom field before re-opening an issue, you can! Check out the blog post that explains how you can use the user condition for different tiers of support in an organisation and working out if a user commenting is the customer

User condition

TIP

Service Desk specific checks such as 'User is in organization' or 'User is a customer' are only available in Jira 7.3+ and Service Desk 3.3+.