Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Original Estimate: populate automatically

Ross Henderson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 23, 2021

Hi all,

We seem to be having an issue where the Original Estimate field is not being populated. This is a field that my product owner and I have never populated, and it's never been an issue in our reporting until now. We used to set the Story Points which automatically filled in the Remaining Estimate (1SP = 1 Day), but we swear this used to also populate Original Estimate.

1: Were we wrong and this wasn't automatically populated?

2: How can we set the workflow to automatically set this depending on the initial remaining value?

1 answer

1 accepted

0 votes
Answer accepted
Andy Heinzer
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 27, 2021

Hi Ross,

I understand that the original estimate field is not being populated any more.  This is a system field that is being calculated based off your estimates.  Please see Configure estimation and tracking for more details. 

I don't think you were wrong, this likely was being automatically populated.  However this is not something that is based on the remaining value, nor can we change it to that.  But instead it was based on the value estimated for that issue before a sprint.  As an issue moves through a sprint, if it's not completed, it could be pushed into the backlog or onto a future sprint.  It's also possible that the issue can have it's estimate change, but this doesn't change the original estimate.  That is bound to the issue at the time the the sprint is started that it was assigned to.

It could be that some other value has changed in regards to the estimations on this board that might account for the change in behavior here.

Andy

Ross Henderson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 4, 2021

I see. So is this possibly caused by adding the Story Point estimate to it as we move it into a sprint, instead of having the Story Point estimate attached to it beforehand? A Story Point estimate has to be provided to any ticket we put into a sprint, so there is always that, I am just wondering if it's because it isn't done before we try and move it?

Edit: I have just tested my hypothesis, and it's not correct.

I will have a look at the link you've provided and see if that resolves the problem, thanks.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events