We use Original Estimate for the obvious, but this does not mean it cannot change. When it changes the Remaining Estimate stays calculated based on the previous value and it needs to be adjusted manually which can be a pain and lead to people forgetting to do it or inaccuracy. Original Estimate is dynamic hence Remaining Estimate should be dynamic too.
We have created a UD field to enter the "Fixed Original Estimate" in case this needed to be reported plus whether there have been changes can be investigated through the issue/task history.
Is it possible to make Remaining Estimate to adjust automatically when Original Estimate changes so that this does not need to be done manually?
I believe that original and remaining estimate are native JIRA fields hence no customisation is allowed.
I know that once you start logging work the remaining estimate is worked out as a deduction from original estimate. However, the issue comes if you change the original estimate once work had already been logged because then the remaining estimate is still calculated based on the original value.
In the attached example original estimate was 2d. I started to log work. Then I set the estimate to 3d but as you can see the remaining estimate keeps on being calculated taking 2d as the estimate which is wrong. When I reach 2d logged work it will say remaining estimate is 0 for that and for any further logged work.
Has anybody experience the same thing? Is there any fix? We are running on version 6.2
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
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!
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