After resolving the issue original estimate sets to zero

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 ?

6 answers

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.

  1. Does this often happen when you are only transitioning the issue to Resolved?
  2. 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?
  3. What are the transitions that caused this (Open > Resolved; In Progress > Resolved; Open > Closed; In Progress > Closed; etc)?

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.

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.

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 ]

Thanks Aaron,

This appears to be working

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

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,937 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot