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; } } }

What is the difference between the 'Story Points' and 'Story point estimate' fields?

Mike Heyns

In Field Configuration I noticed both:

Story Points
Story point estimate

Screenshot from 2018-10-01 18-44-12.png

In our Board Settings we use Story Points for estimation:

Screenshot from 2018-10-01 18-44-45.png

But the new issue view shows the other field. Confused, I enabled both in the Screen Configuration.

Screenshot from 2018-10-01 18-43-56.png

The old view shows both as:

Screenshot from 2018-10-01 18-43-45.png

The new view shows them as:

Screenshot from 2018-10-01 18-42-55.png

Q: What is the difference between them? Why the additional (locked) field?

Accepted answers

larry_lowe

@Mike Heyns

I was also concerned about this field, and reached out to Atlassian directly. Here's what i was told:

The field "Story Point Estimate" is a JIra default field. This field belongs to the project template "Next-Gen" (also known as Agility). The main difference between this field and the field "Story points" is that the "Story points" field (a field which belongs to the "classic" projects) allows you to edit its context, while "Story Point Estimate" is locked.
If you want to learn more about "Next-gen" projects, we recommend you to read the documentation linked below:
https://confluence.atlassian.com/jirasoftwarecloud/get-started-with-agility-boards-945104903.html

Stephen Denman

It was added by this
https://confluence.atlassian.com/jirasoftwarecloud/estimation-959303560.html

But I have no idea what the point or difference is - whats the difference between "Story Points" and "Story Point Estimate"? - they are both estimates

All comments

Mohamed Benziane

Hello @Mike Heyns

I think you'll find some answer here.

https://community.atlassian.com/t5/Jira-Core-questions/What-is-the-difference-between-estimate-and-story-points/qaq-p/125305

Hope this helps

Regards

Michael Heyns_fbkh8w

Hi @Mohamed Benziane

I came across that answer earlier and it appears to be about time estimate not "Story point estimate".

Thank you for referencing it.

Nic Brough -Adaptavist-

It's hard to say what the difference is, because we don't know what your administrators were asked to set up or why.

I would ask your admins what the intention behind this was. Generally, you don't want to have two separate estimates for story points (or any other form of estimation), so your users have done something odd here for a reason we don't know.

Michael Heyns_fbkh8w

Hi Nic

I'm the admin in this case. No modifications where made with regards to Story Points.

From what I recall, 'Story point estimate' didn't use to exist.

Also, I didn't know field labels were configurable depending on view (see old vs new above)

Nic Brough -Adaptavist-

Sorry, I was not explicit enough there, and you've missed the point.

>'Story point estimate' didn't use to exist.

One of your administrators has added that field.

You need to ask them why, because it's probably of no use as it's unlikely to do what they intended.

It's not native to Jira and it's not something created by an App that I know of (and an admin would have had to install an App even if it was done that way).

Tarun Sapra

Hello @Nic Brough -Adaptavist-

I also noticed the "Story points estimate" field in a test cloud Jira instance which I have access to, it's a locked field and thus can't be added by an outside Jira administrator. Also in the first screenshot shared by @Michael Heyns it's displayed as an locked field.

Alex Lewis

Hi,

Did/Do you by any chance have Jira Portfolio installed?

I see the same field and that field was not added manually by an Admin (I'm one of them).

Cheers

Mike Heyns

Hi @Alex Lewis

We do not have Jira Portfolio added

Alex Lewis

Ah well, just a long shot

larry_lowe

I see that field, and I recently installed Portfolio. I suspect that it came from there, but it could also be from any other add-on.

larry_lowe

@Mike Heyns

I was also concerned about this field, and reached out to Atlassian directly. Here's what i was told:

The field "Story Point Estimate" is a JIra default field. This field belongs to the project template "Next-Gen" (also known as Agility). The main difference between this field and the field "Story points" is that the "Story points" field (a field which belongs to the "classic" projects) allows you to edit its context, while "Story Point Estimate" is locked.
If you want to learn more about "Next-gen" projects, we recommend you to read the documentation linked below:
https://confluence.atlassian.com/jirasoftwarecloud/get-started-with-agility-boards-945104903.html

Tarun Sapra

Having two similar fields will just create lot of confusion for admins and for users as well, especially while entering JQL queries as both fields will appear in the drop-down.

Stephen Denman

It was added by this
https://confluence.atlassian.com/jirasoftwarecloud/estimation-959303560.html

But I have no idea what the point or difference is - whats the difference between "Story Points" and "Story Point Estimate"? - they are both estimates

Steve Revill_fg8tnl

We couldn't tell the difference either, so we arbitrarily chose "Story point estimate", given we were doing estimation. It now seems this doesn't appear in the burndown/up charts, which rather defeats the point...

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