Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,294,588
Community Members
 
Community Events
165
Community Groups

Board Estimation Statistic vs. native Story point estimate field

Edited

Hi!

We are using Jira Software Cloud and I have a question about the native Jira custom field called Story point estimate and why it's not possible to set it up as Estimation Statistics for a Scrum board of company-managed project? 

Story point estimate field is configured to be available for all issue types in all projects. Type of this field is not the number field but it says Type = Story point estimate value and this field is locked. It's possible to set this field for a screen but it's not possible to set it as Estimation Statistic (field won't appear in the drop-down, my guess is because it's not a number field)

The official documentation between Cloud and DC version is different but none of them mention the native field.

What Story point estimate represents? Where is it used? Do I really need to create a custom number field called Story points and use that for my scrum boards?

 

Thanks for any clues!

1 answer

1 accepted

1 vote
Answer accepted

Hi @Gabriela Molitoriszova 

Company-managed projects (CMP) use the Story points field and Team-managed projects (TMP) use the Story point estimate field.  These represent the same thing (a relative sizing measure), but cannot be used interchangeably between types of projects.

I am guessing you are using a CMP with a board filter spanning both CMP and TMP projects.  Is that correct?

Kind regards,
Bill

Hi @Bill Sheboy 

Thanks! This is what I was looking for, my main confusion was about the type of custom field - as one is a type "story point value" and the second is a regular "number field" and the fact that the Story point estimate field is locked in configuration but Story points field is not. I'm missing this piece of information in the official documentation. 

We are not using TMP at all, we have only CMP, thus my confusion I guess.

Like Bill Sheboy likes this

Those two fields/design choice cause quite a bit of confusion, so we are not alone on that point  :^)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,225 views 35 44
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you