nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Story Points Estimate Not Showing on Backlog Issue

Oshadhi Vindhyani

Hello,

Our story point estimation shows on inside the issue but not on backlog. This is happening randomly. Only for some issues. As in attached image 1 & 2. Any idea what cause this problem. And how to fix it?

We use planning poker for story points estimation.

Jira cloud standard package
User Admin access

For example : issue number 120 has 8 points , and issue number 153 has 3 points, 3 is showing 8 is not showing.

Image 1

Image 2

Accepted answers

Nic Brough -Adaptavist-

Hi Oshadhi,

The - means that the Story points field is empty. The fact that other issues are showing their story points tells us that the backlog is working correctly, so the only thing I can think of is that you have a duplicated field which people are using instead of the story points field you've chosen to estimate with.

I also note you have a broken workflow - there's a load of stuff in your backlog that is resolved, they should not be there.

Bill Sheboy

Hi @Oshadhi Vindhyani

It appears you are using a team-managed project. Please confirm that by checking the project type at the lower-left side of the page's expanding area.

And if you are using a team-managed project, have you checked if someone has added another field named "Story point estimate"? That could certainly cause the symptom.

Kind regards,
Bill

All comments

Nic Brough -Adaptavist-

Hi Oshadhi,

I also note you have a broken workflow - there's a load of stuff in your backlog that is resolved, they should not be there.

Bill Sheboy

Hi @Oshadhi Vindhyani

It appears you are using a team-managed project. Please confirm that by checking the project type at the lower-left side of the page's expanding area.

And if you are using a team-managed project, have you checked if someone has added another field named "Story point estimate"? That could certainly cause the symptom.

Kind regards,
Bill

Oshadhi Vindhyani

Hi @Bill Sheboy
Sorry I forgot to mentioned I use company managed project. Yes. I think my team lead accidently used the "Story point estimate" field. Thank you so much.

Oshadhi Vindhyani

Hi @Nic Brough -Adaptavist-

Yes. Some of story points added to story point estimate field. I didn't notice that earlier.

This is the method I follow. Kindly let me know If I'm doing this wrong. I'm new to all this stuff.
They were my current sprint's resolved issues. Once sprint completed they'll be gone. Is that okay?
And on the image 2. they were on backlog. We added all the task need to be done end of the development. And for each sprint we move selected task to sprint.

Bill Sheboy

I am glad to learn you resolved that.

There is an open suggestion to untangle the design decision to create two different story point fields: the existing one for company-managed (Story points) and the one added for team-managed (Story point estimate). To follow any action on that, please watch this one:

https://jira.atlassian.com/browse/JSWCLOUD-17173

Nic Brough -Adaptavist-

Ok, that explains it.

A board and its backlog work on a single estimate field, like us humans, they can't work with lots of data in different disparate places.

From what you say, there is nothing wrong with what you are doing other than using different fields for the estimates. If you can get all your story points values into the same field, then everything should fall into place for you.

Oshadhi Vindhyani

@Nic Brough -Adaptavist- Thank you so much for your explanation & your time. Really appreciate it.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-administration

story-points