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 Point Estimate field not showing in actual Story in Teame Managed Space

Ivana Mogin

HI ,

I have setup a team-managed space and have Backlog and Sprints setup. I have configured card fields for the Stories.

Story points Estimate field is in the configuration list for the Story fields, but when I am in the actual Story, it is not showing Story Point Estimate field..

I have checked my Estimates setting, it is set to Estimation - story points.

So in the actual story, for wxample LT-17, I click on Menu (...) ---> Configure and get the list of all the fields. ''Story point estimate' field is on the left, so it should be showing along all other fields, but when I save the config and go to an actual ticket, the Estimate field is not there.

The strange thing is that it is there on the backlog view (one line view for each item, next to short description, priority and assigned to. If I try to enter estimate value there, when I click on 'Ok' it saves it on that one line, but as soon as I edit the Story, the estimate value goes back to '-' and the field is still not in the Story details.

Could someone please help me with making this field accessible since it is obviously crucial for the Sprint velocity etc.

Thanks,

Ivana

Accepted answers

Arkadiusz Wroblewski

Hello @Ivana Mogin

There was quite similar Topic in the past

https://community.atlassian.com/forums/Jira-questions/Not-able-to-add-Story-point-Estimate-on-creating-the-Jira/qaq-p/2862516

PS: try removing the Story point estimate field from the Story work type configuration, saving, then adding it back again to the Context fields section. And check how behave then.

Best,

Arek 🤠

All comments

Ignacio Vera

Hi @Ivana Mogin

Is the field on this view? If it's under hide when empty you won't see it in existing tickets

Arkadiusz Wroblewski

Hello @Ivana Mogin

There was quite similar Topic in the past

https://community.atlassian.com/forums/Jira-questions/Not-able-to-add-Story-point-Estimate-on-creating-the-Jira/qaq-p/2862516

PS: try removing the Story point estimate field from the Story work type configuration, saving, then adding it back again to the Context fields section. And check how behave then.

Best,

Arek 🤠

Julien Morel_fbmylg

Hi @Ivana Mogin,

One extra thing I would check is whether the field is being hidden because it is empty on the issue view. In team-managed projects, the issue layout can include the field but still keep empty fields out of sight until you expand/show the hidden fields area.

I would try this sequence:

1. Open one affected story and use Configure fields / issue layout again.

2. Make sure Story point estimate is in the visible/context fields area, not only available on the left.

3. On the story itself, look for hidden fields or a "show more fields" area and see whether the estimate field appears there.

4. Add a small test estimate directly on the issue view, then refresh the backlog and check whether the value stays.

If it still saves briefly in the backlog and then reverts to -, that feels less like a card-field setting and more like either the issue layout/field visibility or a project-specific field context problem. In that case I would test with a brand-new story in the same project, because it helps separate a layout problem from a problem with only existing issues.

Ivana Mogin

Hi Arek,

Thank you very much, this solution has worked for me. It is a Jira bug. Possibly related to the fact that I have done CSV import of the items to create space backlog.

In a nutshell, remove Story Points estimate field from the space then add it back to the space and assign to Work items you want and it is showing when editing actual work.

The best part is, that values entered previously against Stories in the Backlog view (one line per story) are retained and showing in the field.

Thank you,

Ivana

Ivana Mogin

Thank you. I tried but no success. The solution below (remove field from space then add it back) seems to be the solution.

Ivana Mogin

Hi Ignacio,

Thank you very much for your answer. It was just not hidden, but removing it from the space and then adding back seems to do the trick!

Ivana

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