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 not consider remaining estimate on closed issues in Tempo planner

Marketa Dvorack1

Hi,

we have a problem with users' capacity calculation, which goes under zero because of remaining estimate on issues that have already been resolved.

We would like to have an option to choose if to consider or not the remaining estimate on the resolved issues for the users' capacity value. Ideally on team level. Is there such a thing to set up?

Thank you for any ideas.

Accepted answers

All comments

Jeremy Gaudet

I don't know if this helps, but I was asked to modify our workflow such that the "Close" transition sets the remaining estimate to '0'. That would be per-project, not per-team, but you could check the assignee and zero it out selectively.

Marketa Dvorack1

Hi Jeremy, thanks for your response, but I really don't want to lose that data only to achieve some kind of a workaround, you know? I believe it should be only a matter of data visualization not manipulation. Ideally:)

Albert Hauksson

Hi Marketa and Jeremy, This would also be the recommended workaround from Tempo. Regards, Albert - Tempo Team

Marketa Dvorack1

Hi Albert, I will repeat - you're telling me seriously that for a simple visualization of a piece of data, I have to LOSE data? It doesn't seem to me that difficult to add a flag to the Planner ui "consider/not consider remaining on Closed", but apart from that, seriously. Deleting data, which is always a great loss, on purpose and call it workaround? Impossible.

Gebsun

Log Work Utilities add-on allows to clear remaining estimate on issue close/resolve without a need to modify workflow: https://marketplace.atlassian.com/plugins/com.gebsun.plugins.jira.log-work-utilities/server/overview

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-core

tempo-planner

capacity

remaining-estimate