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 custom field

Nadine Fontannaz_4zpax3

It seems that I have 2 custom fields:

1. Story Points

2. Story points estimate

Question 1 : I've activated both for my screen but when i look into a story, it displays twice: Story points estimate. Why ?

Question 2: I don't know in which field I have to add the value, as the label of the custom field is equal.

Question 3: The custom field "Story points estimate" is LOCKED in my jira Cloud. How can I unlock it? I would like to delete it.

Question 4: How do I do to display by default a custom field on a "create story" template? It's activated in the configuration field screen but it does not appear automatically in the screen when creating a story https://pix4dbug.atlassian.net/secure/admin/ConfigureFieldScreen.jspa?id=11011

Accepted answers

Petter Gonçalves

Hello @Nadine Fontannaz

I understand how much confusion these both fields displaying in your issue view can cause to you. Please, allow me to better explain the behavior you are facing:

Currently, you have both Story Points and Story Point Estimate fields in your project screens.

There's a bug in JIRA 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.

Since you are using a classic project, here's what you should do:

- Navigate to your project > Project settings > Screens

- Remove the Story Point Estimate field from your project screens

Doing the steps above, you will see that one of the Story Point Estimate fields will disappear from your issue view. The one which remains should be the correct field to add your estimations.

Let me know if this information helps.

All comments

Tarun Sapra

Hello @Nadine Fontannaz

Story points vs Story points estimate field

Please see the answer below from

Petterson Goncalves (Atlassian team)

After some time searching and verifying the Story Points Estimate field, I was able to get a clear piece of information about the use of both fields:

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

Both project types 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

That been said, the time tracking measure will only work for your reports if you use the correct field to do it, depending on your project type.

That's why we should avoid adding the Story Point Estimate field to Classic project or the Story Points on Classic projects.

Let me know if this information helps.

https://community.atlassian.com/t5/Jira-Software-questions/Story-point-and-story-point-estimate-duplicate-fields/qaq-p/904742

Also, you can't delete locked fields.

Hope this helps.

Nadine Fontannaz_4zpax3

Thanks @Petter Gonçalves

I am using a Classic projects and I would like to see only the Story Points field then. I am seeing twice the Story point estimate field. Why? Which one should I use then?

Screenshot 2019-04-23 at 16.51.19.png

Petter Gonçalves

Hello @Nadine Fontannaz

I understand how much confusion these both fields displaying in your issue view can cause to you. Please, allow me to better explain the behavior you are facing:

Currently, you have both Story Points and Story Point Estimate fields in your project screens.

Since you are using a classic project, here's what you should do:

- Navigate to your project > Project settings > Screens

- Remove the Story Point Estimate field from your project screens

Doing the steps above, you will see that one of the Story Point Estimate fields will disappear from your issue view. The one which remains should be the correct field to add your estimations.

Let me know if this information helps.

Nadine Fontannaz_4zpax3

@Petter Gonçalves It works !!! Thanks a lot !!!

Petter Gonçalves

You are welcome, @Nadine Fontannaz

Have a nice day and please don't hesitate to contact us again every time you need!

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