Story point/Story point estimate fields

Shweta Pai
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 5, 2019

After I updated the story point estimate field, it started showing up twice on the JIRA card. I am also using JIRA structure cloud  (EAP) and changing estimates there.

Story point issue.PNG

2 answers

2 accepted

1 vote
Answer accepted
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 6, 2019

Hello Shweta,

To add in on what @Petter Gonçalves noted above, this is Primarily the following BUG for the naming rendering issue:

And it ties to the following Subtask that is a child issue of this Feature Improvement story for next gen projects, and is explained in more detail the plans for the fields in the comment section and how the field duplication is occuring on the backend:

Regards,
Earl

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

Hello Shweta,

Welcome to Atlassian Community.

Today, your project templates are split into two types on JIRA Cloud: Classic and Next-gen projects.

As you may know, both projects use their own issue types and have different time tracking methods, which uses two different fields:

- 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

The problem you are facing happens and someone wrongly adds the Story Point Estimate field of the Next-gen projects in the classic project screens and start using the new issue view on it.

Doing the steps above will cause the following behavior:

- The Story Point Estimate of next-gen projects will be added to the issues, but will not be applied to your classic board estimation since it is only applicable to Next-gen boards

- In the new issue view, the Story Points field name will change to Story Point Estimate in order to keep both Next-gen and Classic projects with a similar view and avoid confusion

That been said, you can do the following steps to properly fix your project view:

1 - Turn-off the new issue view on your personal settings - It will change the Story Point Estimate field name back to Story Points so you will be able to identify which field is related to it

2 - Sum the Story points that were wrongly added to the Story Point Estimate in the Story Points field of your Stories

3 - Navigate to your project > Project settings > Screens and remove the Story Points Estimate field, leaving only the Story Points in your project screens

Let me know if this information helps, Shweta.

Suggest an answer

Log in or Sign up to answer