Forums

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

How do I get a sum of all the story points in a sprint for next-gen UI?

Deleted user May 24, 2019

I'm on Jira Cloud, next-gen UI.

So I've read that we should be using Story Point Estimate for next-gen, and we've done that for our stories. But the backlog does not show how many points are in the sprint!

When I try to change the Board Settings > Estimate to Story Point, it seems to be pulling from the classic field, not the new field, so all the colored circles are blank?

What am I doing wrong?

1 answer

0 votes
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 27, 2019

Hello Jocelyn,

Just to make sure we are on the same page, I would like to clarify the concepts of the Next-gen projects and New issue View since they are two different features:

- The new issue view is only a new layout of JIRA software, which can be configured on Classic and Next-gen projects, however, can only be turned off in Classic projects.

- Next-gen is a new template of projects, which offers you less and simpler features to work on your projects and can only be used with the New issue View.

I believe you are using a Classic project with the New issue View of JIRA since Next-gen projects do not have the Board Settings option as you mentioned:

When I try to change the Board Settings > Estimate to Story Point, it seems to be pulling from the classic field, not the new field, so all the colored circles are blank?

That been said, the problem you are facing usually happens in a Classic project when you try to use the Story Point Estimate field from Next-gen Projects instead of the Story Points field of classic projects.

Additionally, there a bug that makes the field Story Points displays as Story Point Estimate in the New issue view although it's still displayed as Story Points when you go to Project settings > Screens, which causes even more confusion.

With this information in mind, please make sure you have added the correct field for your project screens (Story Point), removing the other one to avoid more confusion:

1 - Navigate to project > Project settings > Screens

2 - Remove the Story Point Estimate field, Keeping the Story point field

Let me know if this information makes sense.

Deleted user May 28, 2019

Yes, you're right! I am in classic scrum project with new issue view.

However, the problem I'm now running into is that when I'm creating or editing a single issue, it ONLY displays Story Point Estimate (from the story point estimate field), and does not show Story Points at all, even though I've updated the Issue configuration to display both. Is something wrong with my config?

jira_issue.png

Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 28, 2019

Hello Jocelyn,

That's is expected behavior.

JIRA has one specific field to track each project type and a different field might not work:

- On Classic projects, the estimation is measured on the Story Points field

- On Next-gen projects, the estimation is measured on the Story Point Estimate field

Using the wrong field, the estimation will not appear in the board, just like your screenshot display.

The one which is displaying correctly is the Story Point field, although it is displayed as Story Point Estimate because of the mentioned bug.

Please, keep using the Story Point field and remove the Story Point Estimate from your classic project, so the estimation will be properly displayed.

Deleted user May 28, 2019

I have found the true source of the issue! Most of my settings are correct, with one exception .. listing for future searchers.

At some point during setup attempting to de-dup the two, I had hidden the Story Points field under Jira Settings > Custom Fields, so it didn't show up regardless of my board settings. Setting it to show fixed things.

Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 29, 2019

Hello Jocelyn,

I'm glad to know you were able to find the root cause of the issue.

Let me know if there's anything else I can help with.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events