nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to Calculate Percentage Complete based on timetracking of child issues

Jeffrey_Denton

I've created an automation, manual trigger for now, and please avoid the logs as I was debugging. I see the issue is on the Edit Issue Action.

{{lookupIssues.timetracking.timeSpentSeconds.sum.divide(3600).divide(lookupIssues.timetracking.timeSpentSeconds.sum.divide(3600).add(lookupIssues.timetracking.remainingEstimateSeconds.sum.divide(3600))).multiply(100).round}}

It's providing an incorrect calculation of 900%. Here is my audit log. screencapture-rk-industries-atlassian-net-jira-settings-automation-2025-01-19-21_32_39-edit.png

Here is my automation

screencapture-rk-industries-atlassian-net-jira-settings-automation-2025-01-19-21_34_39-edit (1).png

Accepted answers

Bill Sheboy

Hi @Jeffrey_Denton

Short answer: I recommend using the longer math format for this calculation, such as with this:

{{#=}}ROUND( {{lookupIssues.timetracking.timeSpentSeconds.sum}} / ( {{lookupIssues.timetracking.timeSpentSeconds.sum}} + {{lookupIssues.timetracking.remainingEstimateSeconds.sum}} ) * 100, 0){{/}}

As a percentage is needed, dividing by 3600 for each value may be removed.

For the rule symptom...

I hypothesize there are two things causing the incorrect value: a racetrack error / order of processing, and inline math performing integer division.

Racetrack error / order of processing
- Each of those lookups is iterating over the list of issues, then parsing the time tracking to sum the field, and then performing a division. As that is happening three times within the single inline expression, it could be processing in an unexpected order.
inline math with integer division
- The timetracking values in the expression are integers, and that typing is preserved, left-to-right in the processing. This will cause both potential rounding errors (truncating up to 1799 seconds per value) and not produce the percentage expected as the value before the multiplication by 100 will be 0 or more (with no decimal digits).

Kind regards,
Bill

All comments

Ste Wright

Hi @Jeffrey_Denton

Can I clarify, what are you trying to calculate within the Automation Rule?

Is it the percentage of time left based on original estimate vs remaining estimate? Or is it based on time spent vs original estimate?

Ste

Jeffrey_Denton

Thank you. I'm trying to sum up all children task to get this equation:

Screenshot 2025-01-20 055143 JIRA.jpg

Bill Sheboy

Hi @Jeffrey_Denton

Short answer: I recommend using the longer math format for this calculation, such as with this:

{{#=}}ROUND( {{lookupIssues.timetracking.timeSpentSeconds.sum}} / ( {{lookupIssues.timetracking.timeSpentSeconds.sum}} + {{lookupIssues.timetracking.remainingEstimateSeconds.sum}} ) * 100, 0){{/}}

As a percentage is needed, dividing by 3600 for each value may be removed.

For the rule symptom...

I hypothesize there are two things causing the incorrect value: a racetrack error / order of processing, and inline math performing integer division.

Racetrack error / order of processing
- Each of those lookups is iterating over the list of issues, then parsing the time tracking to sum the field, and then performing a division. As that is happening three times within the single inline expression, it could be processing in an unexpected order.
inline math with integer division
- The timetracking values in the expression are integers, and that typing is preserved, left-to-right in the processing. This will cause both potential rounding errors (truncating up to 1799 seconds per value) and not produce the percentage expected as the value before the multiplication by 100 will be 0 or more (with no decimal digits).

Kind regards,
Bill

Jeffrey_Denton

Bill, I plugged in the automation and it worked swimmingly. thank you for cutting to the chase. I'm going to take a minute to process my solution vs your solution and the information you presented. Thank you!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud