Story points estimate disappears from JIRA Backlog board even if the value of Story points remains
Asked by Rupesh Mehta:

I have configured Estimation method as Story points for one of my project.

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

Now when I go to backlog board view. I am not able to see the Story points values updated in the estimation field even if the Story points are defined in the Story.

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

But when I click on the story, it appears but when I refresh the page, it again disappears. I am not sure whats exactly happening. Because of this I had to add Story points as an additional field in the "Card layout"

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


Answers:
author: L?gia Zanchet
body: Hello Rupesh Mehta,

Welcome to our community!

As Marc mentioned, it would be best for our team to analyze this issue within a ticket.

If you recently imported data to your site, this could be the root cause. It's worth checking your custom fields. Here's how:

1. Click the cog icon for **Settings**.
2. Navigate to **Issues \> Custom Fields**.
3. Search for **Story Point** and click the three dots (**...**) next to it.
4. Select **Default Value and Context**.

Check if the Story Point field has multiple contexts. If one of the contexts has an empty issue type, you can delete that context.

This is a known bug, identified as [**JRACLOUD-83243**.](https://jira.atlassian.com/browse/JRACLOUD-83243)

Thanks!

comments: author: Rupesh Mehta
body: Hi [@L?gia Zanchet](/t5/user/viewprofilepage/user-id/4830848) ,

Thanks for your inputs. It works (estimation values persists) when I deleted the Default Context but the field disappears from all the issue screens. If I get the default context added, the field shows up on all the relevant screens but the estimation vanishes. How to go about it on this?

Thanks!!


author: L?gia Zanchet
body: Hi, adding the context back will allow you to add the field back to the screen.  
As per testing, this won't happen automatically, I'm afraid.


author: Rupesh Mehta
body: Thanks [@L?gia Zanchet](/t5/user/viewprofilepage/user-id/4830848) . Then I have to wait till the time [JRACLOUD-83243](https://jira.atlassian.com/browse/JRACLOUD-83243) bug gets resolved.


author: Marc - Devoteam
body: Hi [@Rupesh Mehta](/t5/user/viewprofilepage/user-id/5559081)

Are you using the Story Points field on both places, or are you using Story Point Estimate as well.

This could be the reason as, the Story Point Estimate field is used only in Team Managed projects, and Story Points in Company Managed projects.

comments: author: Rupesh Mehta
body: My all Projects are Company Managed. And I am using Story points only. Not using Story points estimate.


author: Marc - Devoteam
body: Hi [@Rupesh Mehta](/t5/user/viewprofilepage/user-id/5559081)

Check the board setting and under the card layout there is an option for Backlog and Spring board.

They should be equal, on my instance free and company premium one this works as expected.

If this strange behaviour is on any scrum project you use, raise an issue at Atlassian Support.

They can check your instance backend.


author: Rupesh Mehta
body: Hi [@Marc - Devoteam](/t5/user/viewprofilepage/user-id/3796976) ,

They are equal. Still this issue persists.

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


author: Marc - Devoteam
body: Hi [@Rupesh Mehta](/t5/user/viewprofilepage/user-id/5559081)

Then raise an issue with Atlassian Support, to have them check your instance.

Or it could take a while till all is indexed and executed on the backend.

It can't see you doing anything wrong. I tested it and on my site both numbers are correct.


Tags: cloud

jira-cloud