Running into an error when trying to add two custom fields for all issues

Dipen July 1, 2024

Hello team

                     I am working on an automation rule to see if it would work with a small sample of data. However I am running into the following error

Error:

Error Rendering smart values when executing this rule.

Missing parameter(s) for operator +u: +

# of issues for my test - 2

Purpose: get a total of story points committed at the end of the Sprint. 

Attached is the Screen shot of the Automation rule. 

Screenshot 2024-07-01-154432.png

Here's what the automation rule looks like

Line 1 : I am printing the values of the fields before using the summation formula in lines 2 and 3.

The values are as printing correctly for 

Key, Summary, Story point estimate and Aggregated Story points

Line 2: I am trying to add values for Custom fields using up lookupissues - THIS IS NOT working

Line 3: I am trying to add values for Custom fields using a diff way. - That's NOT working either

Line 4: Closing braces for lookup issues. 

The ideal formula would be to update the Aggregate Story points (custom field) with values from Story point estimate (for Issue 1 and Issue 2)

Aggregate Story points = issue1.Story point estimate + issue2.Story point estimate

Not sure if this is a syntax error or fundamentally wrong in the way I am trying to solve this problem.

Any help would be greatly appreciated. 

Thanks

KD

3 answers

1 accepted

1 vote
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 1, 2024

Hello @Dipen 

For line 3 try removing the issue. prefix from both smart values. Because you are trying to access those values from within the block that is iterating through the lookupIssues results, it infers that you are wanting the information for the current issue being printed from that results set. So you don't have to include the issue object reference, just like you didn't include it when you printed the key or summary.

I suspect line 2 is not working because you have it within the block that is iterating through the issues in the lookup list. Again, like above, and field references within that block are inferred to be a reference to the current issue being printed from the results set. Since the value you want is not for a specific instance but rather is a sum across the entire result set, you need to extract that line. I think it would work if you put it either before the {{#lookupIssues}} line, or after line 4.

Dipen July 1, 2024

Trudy

          Your input is greatly appreciated. 

This is what implemented

Story point estimateformula 1: "{{lookupIssues.Story point estimate.sum}}"
{{#lookupIssues}}
* {{key}} {{summary}} {{Story point estimate}} {{Aggregate Story Points}}
Story point estimateformula 2: {{#=}}{{Story point estimate}} +{{Aggregate Story Points}}{{/}}
{{/}}

 

and I am not getting the error any more. 

Working on evaluating the total's to make sure I am getting the correct values. Will keep you posted. 

Thank you once again

KD

Like Trudy Claspill likes this
0 votes
Dipen July 1, 2024

Will do Trudy. 

 

Thank you 

--KD

0 votes
Dipen July 1, 2024

Trudy 

        Thank you for your speedy response. I will implement your feedback and keep you posted on what progress we are making. 

Thank you once again

-KD

Dipen July 1, 2024

Trudy

         Thank you once again. 

Story points evaluated for all the issue's within that Sprint.

Currently I have 2 separate rules for Total Story Points and Completed Story Points. 

Is there anyway to merge the output of both the values in 1 rule to be able to compute the % complete 

Formula I had in mind was

%Complete=Completed Story Points/Total Story Points * 100

Thanks once again for your valuable input

--KD

 

 

Dipen July 1, 2024

This is the rule I have in mind that I am testing with

Screenshot 2024-07-01-164721.png

%complete = (total story point estimate formula 1/ total story point estimate formula 2) *100

Thanks

--kD

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 1, 2024

That sounds like an entirely different question than your original post. I recommend that you start a new Question post for that topic. In it please include screen images of the two separate rules that you are currently using that you want to combine into one rule.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events