Board Insights not showing story estimates
Asked by daitienshi:

Hi all,

I've seen a few posts about this but not really anything that has been able to help me out.

I'm on a company managed instance of JIRA and I've created a board in my project, where I've configured the board to use the Original Story Point Estimate field for estimation.

![board_estimation_field_setting.png](https://community.atlassian.com/t5/image/serverpage/image-id/336112i236D2ECC04B95A05/image-size/large?v=v2&px=999 "board_estimation_field_setting.png")

However, when I go to view the insights for a sprint (and the tasks do indeed have values for the Original Story Points Estimate field), I get the usual message about needing to add estimates.

![board_insights_message.png](https://community.atlassian.com/t5/image/serverpage/image-id/336114iA2FAEFBA666641A3/image-size/large?v=v2&px=999 "board_insights_message.png")

I've tried with both the selected field as well as the migrated version but none seem to work. Has anyone figured this out? Not sure if it's a project setting that needs to be updated, which might be difficult given it's a company-managed instance and our ability to modify project settings are limited.


Answers:
author: Seon Shakespeare
body: Hi [@daitienshi](/t5/user/viewprofilepage/user-id/5522681)

Welcome to the community!

It looks like you've already correctly configured the "Sprint Commitment" section to use the "Original Story Point Estimate" field by updating your "Estimation Method" in the board settings.

My guess is that there might be a mismatch between the estimate field you're using on your issues and the one expected by the report.

**Check for Field Mismatch:**

1. **Issue Details:** Open one of the issues in your sprint that has a story point estimate.
2. **Field Name:** Carefully check the name of the field where you've entered the estimate. Make sure it *exactly* matches the field you've selected in the "Estimation Method" setting in the board settings.

**Additional Tip:**

* If you're using a field with the "(migration)" suffix, try using the standard "Original Story Point Estimate" field (without the suffix) instead, just to see if that makes a difference.

Hope this helps!

comments: author: daitienshi
body: It seems like the field showing in the Estimates tab labeled "Original Story Points Estimate" does not resolve to the same field as any of the ones labeled "Original story points estimate" or "Original story points estimate (migrated)".

![board_estimates_tab.png](https://community.atlassian.com/t5/image/serverpage/image-id/336146i754F26359C8E4600/image-size/large?v=v2&px=999 "board_estimates_tab.png")

However, if I try to use the "Original time estimate" field in the Estimation for insights, it resolves to the "Original Estimate" field from the actual task. It's not exactly what we wanted to see but I'm curious as to why the Original Story Points Estimate field mapping isn't working. Is this a defect that can be logged?


author: Seon Shakespeare
body: Hmm, it does sound like a bug in how Jira's handling the "Original Story Point Estimate" field.

Since you're on a company-managed instance, getting in touch with your Jira admin to investigate may be your best bet:

1. **Show them your findings** (screenshots, inconsistent field names, etc).
2. **If they are unable to resolve, ask them to request help from Atlassian Support.**

Hope this helps!


author: Seon Shakespeare
body: If my answers have helped, feel free to mark my comment as the**accepted solution**, so others can find it easily. Cheers!


Tags: cloud

insights

jira-cloud