Forums

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

Story points estimate disappears from JIRA Backlog board even if the value of Story points remains

Rupesh Mehta August 2, 2024

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

 

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

 

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

 

 

2 answers

0 votes
Lígia Zanchet
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 6, 2024

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.

Thanks!

Rupesh Mehta August 6, 2024

Hi @Lígia Zanchet ,

 

          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!!

Lígia Zanchet
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 7, 2024

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.

Rupesh Mehta August 7, 2024

Thanks @Lígia Zanchet . Then I have to wait till the time JRACLOUD-83243 bug gets resolved. 

0 votes
Marc - Devoteam
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.
August 2, 2024

Hi @Rupesh Mehta 

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.

Rupesh Mehta August 2, 2024

My all Projects are Company Managed. And I am using Story points only. Not using Story points estimate.

Marc - Devoteam
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.
August 2, 2024

Hi @Rupesh Mehta 

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.

Rupesh Mehta August 2, 2024

Hi @Marc - Devoteam ,

They are equal. Still this issue persists.

JIRA_Board_CardLayout.png

Marc - Devoteam
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.
August 2, 2024

Hi @Rupesh Mehta 

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.

Suggest an answer

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

Atlassian Community Events