Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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
Community Members
Community Events
Community Groups

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

Atlassian Community Events