Forums

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

Sum of original estimates for all Tasks in the Sprint

tatevikalaverdyan September 29, 2024

Hi Community,

I try to create automation, which will sum up Original estimates from all tasks in a Sprint and send that Data as a Web Request. For example if I have 3 tasks in sprint X, which have 2, 3 an 5 hours estimation I want to get 10 as a result. 

The problem is that I receive only information from single task not for all together. 


Can you help me find a way? 
My automation is this 

2024-09-29_22-56-37.png

 

 

{ "Sprint":"{{issue.fixversions.name}}", "Original_estimate":"{{issue.timetracking.originalestimate.sum}}" }

1 answer

1 accepted

0 votes
Answer accepted
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.
September 29, 2024

Hi @tatevikalaverdyan 

That may be done using the bulk-handling feature of branches, with the plural {{issues}} smart valuehttps://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html

Rather than using the branch on issues in sprint, please use the branch on JQL to include your test on the issue type.  Then the condition may be removed from the rule.

Kind regards,
Bill

tatevikalaverdyan September 30, 2024

Thanks for the answer @Bill Sheboy 
I still get e-mail for each task in the sprint

This is the e- mail content

{{#issues}}
These issues are in the sprint
"Sprint":"{{issue.fixversions.name}}",
"Original_estimate":"{{issue.originalestimate.sum}}"
{{/}}

 

2024-09-30_14-17-41.png

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.
September 30, 2024

Please re-read my suggestion and that article.  Your rule should look like this:

  • trigger: scheduled with no JQL included in the trigger
  • branch: on JQL to select your issues, and enable the bulk-handling option
    • action: send email, and it should reference the {{issues}} smart value.  Please note that smart value is plural and not the singular {{issue}} one.
tatevikalaverdyan October 2, 2024

Thank you, Can you please help me with email content. Currectly I receive empty mails. Content is as stated in the article.

{{#issues}}
{{issue.timetracking.originalEstimate}}

{{/}}

Is there anything wrong?

 

 

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 2, 2024

When inside of an iterator, such as {{#issues}}...{{/}} the issue prefix is not used; the scope is the iterator.

For example, this would list the issues and their original estimates:

{{#issues}}
* {{key}} -- {{timetracking.orginalEstimate}}
{{/}}

This would sum the values, without the iterator:

{{issues.timetracking.originalEstimateSeconds.sum}}

 

 

tatevikalaverdyan October 3, 2024

!!! Second option worked, thank you 

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer