How can i sum original estimate from sub-tasks to a parernt?

[Rafael Gonçalves Leal]

I'am trying to sum original estimate field from sub-tasks to parent but isnt work.

My automation rule:

Tarefa_ and Bug_ are sub-tasks types.

My tests:

Rule Logs:

I'am getting a success status but the field doesnt update.

[Bill Sheboy · Accepted solution]

Hi @Rafael Gonçalves Leal -- Welcome to the Atlassian Community!

I do not believe all of the subtask issues' fields are loaded into that smart value.  One way to check that is to change your expression to this smart value:

{{issue.subtasks.timetracking.originalEstimateSeconds.sum.divide(60)}}

The Original Estimate smart value is the human-readable one, and cannot be summed.

If that works, great!

If not, instead try using JQL to gather the subtasks for the parent issue, loading them into a Lookup Issues action.  Then sum with this:

{{lookupIssues.timetracking.originalEstimateSeconds.sum.divide(60)}}

Kind regards,
Bill

[Rafael Gonçalves Leal]

It worked very well Bill, thank you so much!!

[Bill Sheboy]

Awesome!

Which one did you use, the first or the second one?

[Rafael Gonçalves Leal]

First one!

[Bill Sheboy]

Thanks; that is useful info for the future.  Even though I suggested that approach...

When looking at the data for a single issue (to check any available smart values) those fields for the subtasks are not loaded:

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

I recently read a backlog item from Atlassian that indicated each reference to an issue in {{issue.subtasks}} by an automation rule leads to a REST API call for each issue!  And so that must be how the data gets dynamically loaded.

[Rafael Gonçalves Leal]

Its good to know about this api. Thanks!

[Rafael Gonçalves Leal]

Hi @Bill Sheboy 

The automatition is still working but i notice a problem. For some reason the Sum of orignal estimate is getting duplicated:

I found that the that is duplicating is that:

The values of those prints are different because they are from diferent tests

I tried to divide that field per 2 in the automation but i got that problem:

The rule:

[Bill Sheboy]

I do not believe that field, aggregatetimeoriginalestimate, is meant to be set as it is calculated dynamically.  Instead only the original estimate or remating estimate can be set.

Would you please post an image of your current, complete rule and the actions?

[Rafael Gonçalves Leal]

[Bill Sheboy]

When setting the original estimate, the units of measure must be provided.  For example:

{{issue.subtasks.timetracking.originalEstimateSeconds.sum.divide(60)}}m

Adding the "m" on the end to indicate minutes.

[Rafael Gonçalves Leal]

No changes. My original estimate field is working well. The problem is the Σ Original estimate. I've found that it's doubling because it's summing the original estimate from subtasks and the original estimate from the history (that is a sum of original estimate from subtasks, which I did with this automation). So maybe we don't need to use an automation to sum up the subtasks' original estimate because the field Σ Original estimate already sums everything up. The problem is that I think it's not possible to show this field on the layout screen.

[Bill Sheboy]

It is possible to add that field to the board and backlog for a Company-managed project.  Have you tried to add it?

[Rafael Gonçalves Leal]

Yes, i tried that:

[Bill Sheboy]

My apologies as I should have actually tested that: it appears the field can be added but it does not display.  Here is a suggestion to fix that: https://jira.atlassian.com/browse/JRACLOUD-79341

A work-around would be:

• add a custom field which can be added to the issue view
• add automation rules, triggered on time logging and changes to the time tracking fields which will update the custom field when the issue (or its children) change

[Rafael Gonçalves Leal]

It would be the same rule that you told me to do before but with a custom field? I tried that but doesn't work. The field got the value changed to 0. What is the type of the custom field that i need to use?

[Bill Sheboy]

If you wanted it as people-friendly, such as "2d 4h", the custom field would be text type. 

I would need to see the specifics how you are setting the field to comment on any problems with the value (if a text field does not work).

[Salim GOMRI]

I used in my own custom field:

{{issue.subtasks.timetracking.originalEstimateSeconds.sum.divide(60)}}

and it works properly