Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Hi, we are running our first sprint and I wanted to start capturing our team's say/do ratio over time. Curious about some best practice ideas as to what field(s) should be used to capture the "committed" story points at the start of the sprint. We are using a very simple to-do, in-progress, done workflow progression if that helps.


Obviously it is easy to capture the story points completed at the end of the sprint , just wanting to consistently capture our commitment at the start of each sprint.






Hi @Glazner_ Dave _TR Commercial Excellence_  -- Welcome to the Atlassian Community!

Are you using Company-managed (formerly called classic) or Team-managed (formerly called next-gen) projects?

  • For Company-managed, the Sprint Report has that information
  • For Team-managed, the Sprint Burn-down Report has that information

For either of those reports, you would need to add up the results to measure/calculate yourself.  There are probably marketplace add-ons to purchase which do this and more...

Or, if you are feeling experimental you could build your own calculation using an automation rule.  You could trigger this based upon Sprint Completion to find that ratio and notify the team by email, Slack, MS Teams, etc.  If you want to try this, here are some sources on automation rules:

If you need help, please post a question and the community will assist.


Best regards,


Like # people like this
Like # people like this

Hi @Glazner_ Dave _TR Commercial Excellence_ ,

Adding to what @Bill Sheboy mentioned before, I would even more encourage you to have a look at the Velocity chart.

It is also a standard report in both team and company managed projects, as long as they are configured to use sprints. They are the exact representation of say/do reporting, as I understand what you are saying.

All you need for that is to fill out the story points field. The issues at the start of your sprint are your commitment. The number of story points delivered is the number of story points of all issues that were in the rightmost column of your board when you complete your sprint.

Like # people like this
Like # people like this
John Funk Community Leader Apr 14, 2021

Hi @Glazner_ Dave _TR Commercial Excellence_  - Did the answers work out for you? 

Like # people like this


Log in or Sign up to comment
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

252 views 2 1
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