Remaining Estimate Not Deducting Done Tasks

[Theresa]

I'm trying to make a gadget that has my stories listed with the remaining time based on how many tasks are to-do or in progress. When I mark items as Done, they are not deducted from the progress bar or remaining estimate column. How can I make the remaining estimate column for my story and deduct the task's original estimate times that are associated with it?

[Theresa]

I wasn't able to make this work with the suggested automation. Does this need to be a specific project type?

[Kelly Arrey]

We've added post functions to our workflow transitions to Done or Closed to clear the Remaining Estimate field.

[Mikael Sandberg]

Hi Theresa,

Welcome to Atlassian Community!

If you go to one of the issues that you moved to done, is the resolution also set? You should see it next to the status with a checkmark. If the resolution is not set then Jira is consider the issue to still be unresolved and that is why it is not deducted from the progress bar. You can learn more about resolution here, Best practices on using the Resolution field. The KB is mentioning that you can add a new transition to set the resolution on done issue, but this can also be done via automation.

[Theresa]

Sorry, I am new to JIRA. What would the automation for this look like?

I tried this but it doesn't work.

When value changes for status

status is done

for parent

edit issue field resolution done

[Theresa]

Also, when I try and add a rule to the workflow, the dropdown list of fields to update doesn't have Resolution as an option. 

[Kelly Arrey]

Hi @Theresa

One way to set Resolution is in the workflow transition to the terminal status: 

• We use a post-function in the Done transition to set Resolution to Done
• We use a validator in the Close transition to prompt the user to enter a Resolution value (you need a transition screen which includes the Resolution field) before the transition can be completed.

For the automation, I think this would do what you need - If I understood @Mikael Sandberg's update correctly, then setting the Resolution on the task will cause it to be excluded from the rollup of the remaining estimate

Hope this helps!

Kel

[Mikael Sandberg]

@Theresa The automation to set the resolution on issues that are already closed/done would look like this:

The one @Kelly Arrey included above would only work on issues that are currently not in a closed/done status, and in that case it is better to use a post function in the workflow instead of using an automation, especially if you are free/standard plan which limits the number of automation executions you have each month.

[Mikael Sandberg]

Because the automation I included above is a scheduled one you can set it to run whenever, once you saved it you have the option to run it right away and after that you can disable it unless you want to run it on a schedule.

[Theresa]

I tried the 

when issue transitions done

if issue matches JQL

type = Task

The edit issue field resolution

Done

This didn't work. I also tried issue type is subtask and story but none of them worked.