Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Special language doesn't work with smart value

Minh Ngô October 9, 2023

I have try to smart values with LookupIssues

For example has field name is Story Points 

{{lookupIssues."Story Points".sum}}

==> Success, value = 38

For example has field name is Nỗ lực thực hiện (MD)

{{lookupIssues."Nỗ lực thực hiện (MD)".sum}}

==> Success, value = 0

I don't know why value return 0.
Any thing suggest for me?

2 answers

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 10, 2023

Hi @Minh Ngô 

Smart values for automation rules are name, spacing, and case-sensitive.  And...the smart value often does not match the displayed field name on the issue views/pages.

Please confirm you have the correct smart value for your field, and that it is supported by automation rules, using this how-to article:

https://confluence.atlassian.com/automation/find-the-smart-value-for-a-field-993924665.html

And just to confirm, does your version of Jira Server automation have the Lookup Issues Action, as some versions do not?

Kind regards,
Bill

Minh Ngô October 11, 2023

Thank , I have checked my version

I am using Jira Data Center v9.4.0 and plugin Automation for Jira version 9.0.2.

Both of them supported smart values and automation rules, lookupIssues. But I think plugin Automation for Jira just support Lookup Issues Action in version 9.0.2, so new features is working not same in Jira Cloud

I have checked the field name in API and it is corret is Nỗ lực thực hiện (MD.
I have tried use customfield_xxxx but it is not working.

I found the information for this. Because Automation for Jira Data Center not support for custom_field:
https://jira.atlassian.com/browse/JIRAAUTOSERVER-877?filter=98700 

Like Marc - Devoteam likes this
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 11, 2023

Thanks for confirming the field, and that is unfortunate about the Data Center implementation of Lookup Issues.  (Originally, the Jira Cloud version also only supported a few fields...and the rest were added about a year later.)

Depending upon how you want to use that field sum, you have 2 possible work-arounds at this time:

  1. If you want to edit an issue using that sum: Create JQL to find your issues, use a Send Web Request action to call the REST API function to search for the issues, and then you can easily sum on the response.  https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828
  2. If you want to send that sum in an email or message: Use a branch or scheduled trigger with the bulk-handling feature of Jira Server/Data Center automation rules: https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html
Like Minh Ngô likes this
0 votes
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 10, 2023

Hi @Minh Ngô 

What is your objective?

{{lookupIssues."Nỗ lực thực hiện (MD)".sum}} will give 0, if it's not a number field.

Can you provide your usecase?

Minh Ngô October 11, 2023

I sure that is number filed but Jira Data Center not support Automation for custom_field


I found the information for this. Because Automation for Jira Data Center not support for custom_field:
https://jira.atlassian.com/browse/JIRAAUTOSERVER-877?filter=98700 

Like Marc - Devoteam likes this

Suggest an answer

Log in or Sign up to answer