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; } } }

After resolving the issue original estimate sets to zero

Kivanc Tuncsav

We have time tracking on our resolve screen on Jira. When a user resolves the issue and logs some work original estimate of the issue becomes zero. TIMEORIGINALESTIMATE colon on [jiradb].[dbo].[jiraissue] table in jira db. An exception : If users enters some log before resolving the issue , the original estimate doesn't become zore on resolution. Do you have any idea what's going on ?

Accepted answers

All comments

Justin Alex Paramanandan

Does this often happen when you are only transitioning the issue to Resolved?
If users enters some log before resolving the issue , the original estimate doesn't become zore on resolution. - does this mean that performing regular work logging before resolving the issue does not set the original estimate to 0?
What are the transitions that caused this (Open > Resolved; In Progress > Resolved; Open > Closed; In Progress > Closed; etc)?

Kivanc Tuncsav

1. Yes it is only happened when transition to Resolved.

2. Yes performing regular work logging does not set the original estimate to 0

3. We have a custom workflow like

Open > Active > Resolved.

More info

There is a Post function on Resolve transition which says :

The Remaining Estimate of the issue will be set to 0.

But it sets the original estimate to 0 . on resolution transition if a worklog is also entered on the resolution screen.

Justin Alex Paramanandan

Hmm, that is indeed true. The post function The Remaining Estimate of the issue will be set to 0. is something that caters for the remaining estimates only. Do you have other plugins that are installed in your instance that adds functionalities to the workflow? Also, can you check whether the Active status and the transition from Active > Resolve has any other post functions?

There were some instances where the Script Runner plugin caused a possible issue with the workflow transitions.

JT4

Justin,

I am experiencing the same issue with post function The Remaining Estimate of the issue will be set to 0. This is the only post function we have on the transition. There are no Conditions or Validator on the transition either.

Here is what the history captures:

Status	In Progress [ 3 ]	Resolved [ 5 ]
Original Estimate	6 hours [ 21600 ]	0 minutes [ 0 ]
Remaining Estimate	6 hours [ 21600 ]	0 minutes [ 0 ]
Resolution		Fixed/Completed [ 1 ]

Aaron Booth

Hi,

I am pretty sure we had this problem as well. I resolved the issue by making the workflow change the Remaining Estimate to 0m instead of 0.

When it was set to 0 the Original Estimate was wiped as well for whatever reason (a bug?).

Give that a shot.

JT4

Thanks Aaron,

This appears to be working

Jeanne Nicole1

This problem may be related to Legacy mode being enabled. That issue is tracked here: https://jira.atlassian.com/browse/JRA-25031

Welcome!

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

Quick Links

Find more posts tagged with

jira

workflow