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 vs Story Point Estimate fields: What feeds the Velocity Chart at the end of the sprint?

Jennifer Dragan

Hey there!

I have read through a few threads and want to make sure I'm setting up proper commitments at the beginning of each sprint so I can review velocity with the team at the end of our sprint. Which field actually fuels the commitment data point on this graph?

Any help is appreciated,

Accepted answers

Bill Sheboy

Hi @Jennifer Dragan -- Welcome to the Atlassian Community!

What type of project are you using: team-managed or company-managed?

Team-managed projects use the Story Point Estimate field and company-managed used the Story Points field.

Best regards,
Bill

All comments

Bill Sheboy

Hi @Jennifer Dragan -- Welcome to the Atlassian Community!

What type of project are you using: team-managed or company-managed?

Team-managed projects use the Story Point Estimate field and company-managed used the Story Points field.

Best regards,
Bill

Jennifer Dragan

Hey Bill,

We are using company-managed projects for all our active projects within jira! Just wanted to confirm--these two fields will work the same (as a commitment metric) based on the project type?

Bill Sheboy

Hi Jennifer,

I am unclear what you mean by a "commitment metric". For each project type, those are the relative-sizing measures supported. When team-managed (formerly next-gen) got added, the Atlassian team apparently did backend improvements leading to the need for the new field.

And, for each respective project type, those fields support the reporting when estimation is used.

Best regards,
Bill

Jennifer Dragan

Okay great. Thanks

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

velocity