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

How to get Velocity chart values using JQL?

Hello, we keep track of our planned-to-done statistics by relying on the Velocity chart report (see image):


How can I get these two values (commitment and completed by sprint) via JQL?

or is there any other possible way to get these two values, or the exact list of issues which summarize those values?

We need this so we can create an Excel report or a Power BI report with such data.


2 answers

0 votes

JQL fetches lists of issues that match criteria, nothing more.  It's up to your reporting to build summaries and sums.

To do this, you do a simple search for "sprint = round 11" and another for "sprint = round 12" and then look at the estimates on the issues combined with their status to work out the numbers you are seeing in that report.

Thing is (if I search for sprint = round 11), story points sum don't match commitment sum nor completed sum. I wanted to know how JIRA calculates both values.

Commitment = sum of story points on the stories when you start the sprint.  This can change if you change the story points on an issue during the sprint (bad practice to do that, but it can be done)

Completed = sum of story points on stories in the last column of the board when you complete the sprint.

Sprint = round 11 will report only on the current issue values

Like Rogelio Vidaurri likes this

Hi @Rogelio Vidaurri 

Due to possible scope changes during the sprint (issues and sizing), the sprint report can show this information and JQL cannot easily do so.  The commitment sum is the total of issues in the sprint when it started progress, and completed sum is the total of issues in the sprint when it completed.

Best regards,


Oddly, sometimes "commitment" value changes during the sprint.


As long as you do not delete issues from your instance, one way to capture "commitment" and ignore other changes is to create custom fields to store "commitment sprint" and "commitment sizing", storing them with an automation rule once the sprint starts.  Those values could then be searched later with JQL.

However at that point of work-arounds, I wonder if the team could pause and consider the problem they are trying to solve... Jira's report can work correctly when there are not scope/sizing changes.  Either one of those changes indicate something a team could discuss, learn why those changes are happening, and consider experiments to try to improve.

Like Rogelio Vidaurri likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

319 views 9 7
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