nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can conditional operators be used in emails created by Automation Rules?

Darryl Lee - CCC

I asked support about this, but figured it might be of interest to the community. Original Summary:

Can conditional operators be used in emails created by Automation Rules to hide fields that are empty?

We would like to send email notifications where fields are displayed only if they are not empty.

I tried this:

{{#=}}IF({{issue.Desired Delivery Date/Time}}!="","<b>Desired Pickup Date/Time:</b> {{issue.Desired Delivery Date/Time}}",""){{/}}

And got this error:

Error rendering smart-values when executing this rule:
Unknown operator ':' at position 17: IF(2020-07-10T20:00:00.0+0000!="",<b>Desired Pickup Date/Time:</b> 2020-07-10T20:00:00.0+0000,)

I tried surrounding the value with quotes

{{#=}}IF({{"issue.Desired Delivery Date/Time}}"!="","<b>Desired Pickup Date/Time:</b> {{issue.Desired Delivery Date/Time}}",""){{/}}

And got this:

Error rendering smart-values when executing this rule:
Missing parameter(s) for operator !=: IF("2020-07-10T20:00:00.0+0000"!="","<b>Desired Pickup Date/Time:</b> 2020-07-10T20:00:00.0+0000","")

Are the Math operators even able to compare string values?

Thanks!

Accepted answers

John Funk

Hi Darryl,

I doubt Automation For Jira is going to be able to do what you have in there, but will let Support provide you with the expert response.

Have you thought about filtering out those emails using JQL and then creating your Email rule just against the appropriate filter(s). You might need to create multiple rules to send various versions of the filters.

Darryl Lee - CCC

JIRA Support got back to me with this answer, which I'm going to mark as correct. :-}

We recently added to support to conditional fields in automation actions and now you can perform some of those logic validations in the action item itself. The syntax would be something like that:
{{#if (issue.duedate.jiraDate.isNotEmpty()) }}
 test: {{issue.duedate}}
{{/}}
The following article will cover this in more details:

New automation smart values in Jira Cloud

Additionally, I successfully tested some other field types:

Priority:

{{issue.description}}
{{#if (issue.priority.isNotEmpty()) }}
<b>Priority:</b> {{issue.priority.name}}
{{/}}

Single-Select Field:

{{#if (issue.Destination.value.isNotEmpty()) }}
<b>Destination</b>: {{issue.Destination.value}}
{{/}}

All comments

John Funk

Hi Darryl,

I doubt Automation For Jira is going to be able to do what you have in there, but will let Support provide you with the expert response.

Darryl Lee - CCC

Hi, yes, looking forward to what Support has to say.

To provide some context, this is a Rule happening On Create for a JSD project that has 6 different Request Types that have slightly different sets of fields.

So the email currently looks like this:

Hello ________ – thank you for your Services Request.

Summary: Move stuff into Lab
Description:
Unpack crates and move equipment into Lab

Requesting Department: Special Projects
Destination:
Desired Pickup Date/Time:
Desired Delivery Date/Time: 2020-06-30T13:00:00.0+0000

But for Services Requests, there is not a Destination or Pickup, so ideally those empty fields would be hidden.

I'm trying avoid having to create a separate email template for each Request Type, since they're *almost* the same except for a few fields.

John Funk

You could do a single rule but have nested if/then statements for each Request Type. Then Copy and paste the email under each Request Type and edit out the fields that would be blank.

Darryl Lee - CCC

Right, I know I could do it in one rule with if/thens. I guess I just miss Velocity templates. :-}

Darryl Lee - CCC

JIRA Support got back to me with this answer, which I'm going to mark as correct. :-}

We recently added to support to conditional fields in automation actions and now you can perform some of those logic validations in the action item itself. The syntax would be something like that:
{{#if (issue.duedate.jiraDate.isNotEmpty()) }}
 test: {{issue.duedate}}
{{/}}
The following article will cover this in more details:

New automation smart values in Jira Cloud

Additionally, I successfully tested some other field types:

Priority:

{{issue.description}}
{{#if (issue.priority.isNotEmpty()) }}
<b>Priority:</b> {{issue.priority.name}}
{{/}}

Single-Select Field:

{{#if (issue.Destination.value.isNotEmpty()) }}
<b>Destination</b>: {{issue.Destination.value}}
{{/}}

Darryl Lee

Ohai - I had forgotten about this answer until somebody recently liked it.

As it turns out, it looks like Automation doesn't even require the isNotEmpty:

I recently used this for a cascading field value:

<b>CRM Access Requirements: {{issue."CRM Access".value}}{{#if(issue."CRM Access".child.value)}} - {{issue."CRM Access".child.value}}{{/}}</b>

It's probably good practice to use it though.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

jira-cloud

addon-com.codebarrel.addons.automation

automation