efficient way using JQL queries to get the ‘Done’ status stories during a sprint duration - velocity

Question

Hello Atlassian Community,

Is there an efficient way using JQL queries (within Jira Cloud) to get the ‘Done’ status stories during the sprint duration?

Some of the stories are carried over to the next sprint but I'm just looking for the velocity of the 'Done' stories within 1 sprint (let's say 2 weeks).

Thank you.

Iryna Komarnitska_SaaSJet_ · Answer

Hi @Marcin Jankielewicz ,

Try using Sprint Report, available in the Time in Status for Jira app (developed by my team).

Note that there is a dropdown in the upper right corner where you can select one of the three parameters for generating a report:

* Story Points. The report calculates data based on the story points field set for each issue in your sprint.
* Issue Count. The report calculates data based on the number of issues in your sprint.
* Original Time. The report calculates data based on the time estimate field set for each issue in your sprint.

In Sprint Structure, you can see the percentage of all completed issues.

Team Velocity - Displays the team's committed and completed values for each sprint during the last sprints from the selected one. The selected sprint would always be the right one on the chart.

There is a Completion rate chart in the lower left corner. The carryover rate will show how many tasks have been moved to the next sprint.

Try it. I hope it will be helpful for you!

Marcin Jankielewicz_xeicol · Answer

Thank you @Mykenna Cepek

What if the story has been tagged let's say with Sprint1 and it wasn't completed within that sprint but then it's now in Sprint 2 but it still has the tag of Sprint1 - I don't want to include this story into my velocity for Sprint1.  What would be the best JQL to obtain that?

Thank you.

Mykenna Cepek · Answer

I'd start with something like this:

Project = ProjKey AND Sprint in openSprints() AND statusCategory = Done

This avoids having to name the sprint explicitly, but assumes you only have one Sprint started for the indicated Project at any one time.

You might also experiment with this in a Jira Filter macro on a Confluence page, giving you an on-demand report. One advantage of this approach is that the page uses consistent (customizable) columns for this report, whereas the "Issue Search" feature in Jira tends to return ad-hoc columns.