Burn down chart don't work

[Christopher Roberts]

In an earlier project we include a time estimate in the "Original Estimate" field and the Burn down chart works perfectly.

In a newer project (created the same way) we are also including a time estimate in the "Original Estimate" field. However when we start a sprint a warning comes up to say something like "these issues do not have a value in the 'Estimate' field". I assume this is also why the burn down chart does not work. I can't even see any "Estimate" field.

What has changed?

Do we have to re-configure Jira to use the Original Estimate field? 

[Andy Heinzer]

HI Christopher,

From the way you have described the problem, it sounds like you are not entering data into the 'story point estimate field on the issue itself.  Jira does allow you to create multiple custom fields of the same name.  So off-hand, my guess would be that your environment could have either multiple such named fields or an addition 'estimate field that is having data added to it.  The burndown report won't be able to pull data from that custom field, but rather would need to pull that data from the system field.

If you're a Jira admin of this Cloud site, you could go to a URL such as /secure/admin/ViewCustomFields.jspa?searchFilter=estimate

This would give you a search of any/all fields in the system that might be called estimate.  In my test Jira Cloud site, I only have one here called 'Story point estimate and this field is noted as Locked.  This is a field created specifically by Jira Software for use in that product.

If that is not the case here, I'd be interested to see if you can create a support case with our Cloud support team to further investigate your specific environment here.

Regards,

Andy

[Christopher Roberts]

Hi Andy,

I performed the search and it is exactly as you found "Story point estimate" with the note LOCKED.

I started new sprints yesterday and again got the warning that the "Estimate" fields are empty.

I don't understand how every reference to estimate is different. Burn down chart uses the term "Original Time Estimate", the warning calls it the "Estimate" field, the tickets uses "Original Estimate", the project settings "Fields" has "Story Points" and your search has "Story point estimate".  Are all these the same thing? 

Are we able to arrange a teleconference or something as this is a big problem. We are currently using work around and exporting the data to excel so we can get useful information out.

Regards,

Chris 

[Andy Heinzer]

Hi Chris,

Our support offerings for Community do not include teleconference.  However as a site admin of Cloud site, you likely are entitled to standard support at least.  You can read more about our Support Offerings in https://confluence.atlassian.com/support/atlassian-support-offerings-193299636.html

The difference between Estimate and Original Estimate are based upon when a sprint is started.  Estimate can be changed at anytime, but when you start a sprint, whatever value that issue has in the estimate at that time, is then recorded in the original estimate.  You are not expected to be able to change the original estimate of that issue once the sprint has started.

But the fact that you are getting this warning that the estimate field is empty would seem to indicate that your site could have more than one such estimate field.   To see if that is the case, I am going to create a support case on your behalf.  This way at least someone from our Cloud support team can take a closer look at your site and perhaps we can find a better answer here that way.

Please see https://getsupport.atlassian.com/servicedesk/customer/portal/42/PSCLOUD-34679

Andy