Im working to sum up several custom fields given some criteria * The number needs to be less than 200 * The field should be skipped if there is no number there. * For example if the numbers in the four of the fields are 1,null,2,900 the answer should be 3 (skipping the null and skipping the 900) * I have the first bullet point figured out and I can sum everything that has data while skkipping things over 200, but my issue occurs when something doesnt have an entry in the field (null). Any ideas? Here is what im running right now. Basically check if the field is less than 200, if it is print it and add to the next number: {{#if(customfield_12863.lte(200))}}{{customfield_12863}}{{/}} + {{#if(customfield_12869.lte(200))}}{{customfield_12869}}{{/}} + {{#if(customfield_12859.lte(200))}}{{customfield_12859}}{{/}}+ {{#if(customfield_12848.lte(200))}}{{customfield_12848}}{{/}} Thanks in advance!

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; } } }

Automation Error - Skipping fields with no entry

Travis Hill_08pum3

Im working to sum up several custom fields given some criteria

The number needs to be less than 200
The field should be skipped if there is no number there.
For example if the numbers in the four of the fields are 1,null,2,900 the answer should be 3 (skipping the null and skipping the 900)
I have the first bullet point figured out and I can sum everything that has data while skkipping things over 200, but my issue occurs when something doesnt have an entry in the field (null).

Any ideas?

Here is what im running right now. Basically check if the field is less than 200, if it is print it and add to the next number:

{{#if(customfield_12863.lte(200))}}{{customfield_12863}}{{/}} + {{#if(customfield_12869.lte(200))}}{{customfield_12869}}{{/}} + {{#if(customfield_12859.lte(200))}}{{customfield_12859}}{{/}}+ {{#if(customfield_12848.lte(200))}}{{customfield_12848}}{{/}}

Thanks in advance!

Accepted answers

Bill Sheboy

Hi @Travis Hill

For a math expression which uses conditional logic, you could handle missing values with:

additional conditions for empty values, which can be problematic to identify for some field types, or
add default values before the expressions

As an example of the second option, add 0 values before the conditional checks:

{{#=}}
   0{{#if(customfield_12863.lte(200))}}{{customfield_12863}}{{/}}
 + 0{{#if(customfield_12869.lte(200))}}{{customfield_12869}}{{/}}
 + 0{{#if(customfield_12859.lte(200))}}{{customfield_12859}}{{/}}
 + 0{{#if(customfield_12848.lte(200))}}{{customfield_12848}}{{/}}
{{/}}

This prevents the conditions from collapsing to null and breaking the math expression.

Kind regards,
Bill

All comments

Tobias H

Hi @Travis Hill!

I'll preface this with that my smart value math if very limited, but I did run into a similar problems when I had to add sums together in an automation some months ago.

As you said yourself, if the field is empty on submission, it fails. You should add an else statement either in the automation component or in the smart value to add a 0 to empty submissions. Then instead of failing on nulls, it will do +0s which won't change your final sum.

TL;DR:

Either use Else component to say "If empty then set 0"
Or try to work it into the math value if you have the knowledge

Bill Sheboy

Hi @Travis Hill

For a math expression which uses conditional logic, you could handle missing values with:

additional conditions for empty values, which can be problematic to identify for some field types, or
add default values before the expressions

As an example of the second option, add 0 values before the conditional checks:

{{#=}}
   0{{#if(customfield_12863.lte(200))}}{{customfield_12863}}{{/}}
 + 0{{#if(customfield_12869.lte(200))}}{{customfield_12869}}{{/}}
 + 0{{#if(customfield_12859.lte(200))}}{{customfield_12859}}{{/}}
 + 0{{#if(customfield_12848.lte(200))}}{{customfield_12848}}{{/}}
{{/}}

This prevents the conditions from collapsing to null and breaking the math expression.

Kind regards,
Bill

Travis Hill_08pum3

Thanks Bill, appreciate the response. In the second instance, if I add a default value before the conditional checks, does it add the 0 to the field itself? Or does it just skip if there is no value in the field? The reason I ask is that this set up is for a ranking mechanism, so automatically adding a 0 to the field would be bad news because it would default everything to the top of our lists.

Travis Hill_08pum3

Thank you Tobias, appreciate the response. Unfortunately I cant default everything to 0 (or any other number) in this instance because the fields are used as a ranking mechanism so it would potentially impact our prioritization lists if we default to another value

Bill Sheboy

Thanks for the additional context, Travis.

I was adding a 0 as a default value before the conditions as you are using math expression. If some other default value is needed for your context, that value will decide how to proceed. For example...

If this is a numerical ranking, where 0 is "higher rank" than 1, you could add a very large default, such as 99999
If this is some other form of ranking, using a math operation may not be appropriate for this case. That is, if the value for a field such as custofield_12863 should not contribute to the ranking, what does that look like in "ranking"?

Travis Hill_08pum3

This is helpful thank you. Ill mess around with this a bit and see what happens.

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-cloud

automation