Use math expression with look up action

Maurice B.

Hey Guys, 

I'm currently struggling with math expressions resulting from a look up action. 

The rule looks like this (removed the content for privacy reasons): 

What I would like to have is a weekly report for all selected issues from the look up action. I have set up a custom numeric field "completion in %" and would like to multiply story points with the completion in % 

As far as I understand the syntax, I tried to use the following math expression: 
{{#=}}{{LookupIssues.Story Points}} * {{LookupIssues.customfield_11965}} / 100{{/}}

(note: for one single issue with manual trigger I used the expression above with "issue.Story points" instead of "LookupIssues.Story Points" and it worked, but this is not what I am looking for)

In the send e-mail action I would like to have one email with a table that contains the result from that math expression for all issues found within the look up action. 

Is there a better way to set up the rule or do you find any mistakes? 

Thank you for your support. 

 

 

 

Bill Sheboy

Hi @Maurice B. 

First, smart values are name, spacing, and case-sensitive.  When an incorrect one is used, it evaluates to null, often leading to expressions failing to work as expected.  The smart value for the lookup issues results is {{lookupIssues}}

Next, the result of a Lookup Issues action is a list of issues, with zero-to-many in the results.  And so they must either be iterated over or summarized for a field, such as with the sum or average functions.

Let's assume you want to list the value for each issue.  To iterate over the issues and perform the math operation, please try this expression:

{{#lookupIssues}}
* {{key}} - {{summary}}: {{#=}}ROUND({{Story points|0}} * {{customfield_11965|0}} / 100, 2){{/}}
{{/}}

I added a default value of 0 for each field to handle cases where the field is not set, and the ROUND() function so you can decide how many decimal places you want to show.  (I used 2 digits for the decimals.)

 

Finally, what type of project are you using: Company-managed or Team-managed?  These use two different "story points" fields, so confirm you are using the correct one:

• Company-managed use "Story points" with the smart value {{issue.Story points}}
• Team-managed use "Story point estimate" with the smart value {{issue.Story point estimate}}

 

Kind regards,
Bill