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 for JIRA - Sum of numeric (decimal) fields doesn't work with lookupissues

Patrick Schmidt_icr0kr

Hi,

I've got a custom numeric field set up in JIRA, which contains decimal numbers, e.g. 8,5.

The comma is used as a decimal separator instead of a dot, as this is the setting for Germany.

{{lookupIssues.My custom field.sum}} returns 0 although the fields are filled with values. I think it has something to do with the decimal separator.

Using issueFunction in JQL returns the expected number, e.g. 57.2

issueFunction in aggregateExpression("Sum of xyz", "MyCustomField.sum()"

Any idea?

Thanks a lot,

Patrick

Accepted answers

All comments

Patrick Schmidt_icr0kr

Hi,

I might be a little closer to a solution. It turns out that {{lookupIssues}} is not able to read the content of my numeric field but {{issues}} does. {{issues}} should also be able to parse a list of issues provided by JQL. {{issues.sum}} doesn't return the expected value.

Bill Sheboy

Hi @Patrick Schmidt

First thing, the {{issues}} smart value (note the plural) is only defined / supported for Jira Server and Data Center versions, not for Jira Cloud. I would not rely upon that smart value for Jira Cloud.

Next, you note that a numeric custom field is not available in the results of Lookup Issues.

Smart values are name, spacing, and case-sensitive. And often the smart value does not match the displayed field name on the issue views. When an incorrect smart value is used in a rule, it evaluates to null and often fails silently.

The how-to article below helps to identify the correct smart value (and custom field id) for any supported fields for automation rules. The essential steps are:

identify an issue which has your field(s)
call a REST API function with a browser to search for your issue:

https://<yourinstanceurl>/rest/api/2/issue/<issuekey>?expand=names

search on the page for your field, such as with CTRL-F
- if you find the field, you will also find the smart value, custom field id, and structure / attributes it has
- if you do not find the field, it is not supported by automation rules

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

If you custom field is from a marketplace addon, that may explain why it is not supported by automation rules.

Kind regards,
Bill

Patrick Schmidt_icr0kr

Hi @Bill Sheboy

thanks for your reply!

I forgot to mention that I'm using JIRA Data Center. I'm aware of the case sensitivity and checked the correct field name through the rest API. What I noticed is that I can't call specific custom fields with their ID, e.g. {{lookupIssues}}{{customfield_123456}} after a JQL lookup, also {{lookupIssues}}{{customfield_123456.sum}} doesn't work. I tried this for several numeric custom fields. I guess I need the correct smart value call with {{issues}} that provides me a sum of my custom field. {{issues}}{{My Custom Field.sum}} only returns one value of the list of issues not a sum of all.

Thanks a lot,

Patrick

Bill Sheboy

Thanks for the confirmation of your Jira version.

To sum a numeric field for a Lookup Issues result set, please use this syntax:

{{lookupIssues.customfield_123456.sum|0}}

I added a default value of 0 to the end to handle the case of all values are empty / null.

Patrick Schmidt_icr0kr

Hi @Bill Sheboy

thanks again! Unfortunately this doesn't work either. I tried several versions, all return a 0.

{{lookupIssues.customfield_123456.sum|0}}

{{lookupIssues."customfield_123456".sum|0}}

 {{lookupIssues.My Custom Field.sum|0}}

{{lookupIssues."My Custom Field".sum|0}}

{{issues.customfield_123456.sum|0}}

The custom field contains decimal values separated by ",".

In JIRA the JQL issueFunction in aggregateExpression("Sum", "MyCustomField.sum()") returns Sum: 32.6.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

automation