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; } } }

How to get Velocity chart values using JQL?

Rogelio Vidaurri

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.

Thanks

Accepted answers

All comments

Nic Brough -Adaptavist-

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.

Rogelio Vidaurri

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.

Bill Sheboy

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.

https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-velocity-chart/

Best regards,

Bill

Rogelio Vidaurri

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

Thanks.

Bill Sheboy

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.

Nic Brough -Adaptavist-

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

Gopichand Menta

can help me in JQL query in Azure Devops?

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

Azure Devops does not have JQL. Could you explain what you are trying to do?

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

atl-orange