How to edit the Velocity Report to only start from a specific Sprint?

[Gráinne]

Hi All,

I would need to be able to filter the Velocity Report to start from a specific Sprint or date. I tried playing around with the board filter but there greater than ">" is not allowed in combination with a sprint and there is no sprint start date > 2024/12/13 option either. I tried removing unnecessary Sprint like

project = X AND sprint not in ("Sprint 35"," Sprint 36"," Sprint 39", "Sprint 40" )

The issue there being if the issue was in one of those Sprints and turns up in a later Sprint the Story points are removed any way from this later Sprint in the velocity report messing up the statistics.

Please add the possibility to add a filter option or a select option for the Sprints shown in the Velocity report. Thank you. 

[Danut M _StonikByte_]

Hi @Gráinne,

Unfortunately, Jira Cloud's velocity report is quite limited and cannot filter by specific time intervals or by sprint names. 

As advised already, you could look for an app on Atlassian Marketplace that offers a report or gadget capable to do this. 

In case you want to try an app, our Great Gadgets app offers a powerful Team Velocity gadget that allows you filter the sprints displayed by time range or by name. 

The gadget is highly customizable, works with any type of estimates, can include sub-tasks, offers additional metrics (such % completion, scope changes, etc), and can display a Data tab with detailed data about every sprint.   

Danut.

[Gráinne]

Hi @Danut M _StonikByte_ Danut,

Thank you for the detailed information regarding the limitations of Jira Cloud's velocity report and the suggestion to explore apps on the Atlassian Marketplace.

I will take a look at the Great Gadgets app you mentioned, as it seems to offer the functionality we need.

I appreciate your assistance and will get back to you if I have any further questions.

Best regards,
Gráinne

[Alexey Pavlenko _App Developer_]

Hi @Gráinne ,

Unfortunately, I didn't get you. If you completed an issue within Sprint 1, reopened it, added it to Sprint 3, and completed it within Sprint 3, then the Velocity Report will show that the issue was completed in both sprints (Sprint 1 and 3). Please elaborate a bit more if your case is different.

Best regards,
Alexey

[Gráinne]

Hi @Alexey Pavlenko _App Developer_ ,

I would like to clarify the sequence of events:

• An issue from Project A was added to Sprint 1 but was not completed as we were awaiting feedback.
• In Sprint 2, Project X was defined, and the aforementioned issue was moved from Project A to Project X.
• The issue was then added again to Sprint 4.

Currently, the Velocity report for Project X indicates that this issue was committed in Sprint 1 but was not completed, even though Project X's first sprint was Sprint 3.

I would like the Velocity report to reflect data starting from Sprint 3 only. But modifying the Board filter of Project X to not show issues from Sprint 1 automatically excludes this issue from the Velocity report in Sprint 4.

Our sprints span multiple projects as developers work on various projects as needed.

Thank you,
Gráinne

[Alexey Pavlenko _App Developer_]

Hi @Gráinne ,

Thank you for the clarification. If it's one time case I am not sure if you need to pay for a custom app. The Sprint Report shows the last 12 sprints. So, over time you won't see Sprint 1 in the report anyway. If you see that it's a recurring case, then my app can help you with that - Multi-team Metrics & Retrospective. With it, you can even construct custom JQL metrics.

Settings for number of sprints (periods):

With the app, you also can:

• Track any custom metric constructed using JQL across any periods - sprints, months, quarters, half-years or years for multiple teams in a single view.
• Conduct in-place retrospectives.
• Compare metrics between teams or periods Identify, quantify, and prioritize reasons behind mediocre performance, and easily justify budget allocation for improvements.
• View dynamics between the current and previous periods.
• View % of a metric relative to Initial or Final Scope.
• Average of metrics for the selected periods.

and much more.

Best regards,
Alexey

[Rahul_RVS]

Hi @Gráinne 

Welcome to the community !!

As suggested by Humashankar, a mktplace app can help here. If you would be interested to try out one, pls do take a look at 
Agile Velocity & Status Gadgets 

The app comes with few dashboard gadgets to track team member's / team's velocity / productivity based on story points / time spent / issue count in a sprint  and also track sprint status with multiple parameters. The app works for past / closed sprints too and can be used to display data for specific sprints as well.

Disclaimer : I am part of the team which developed this app

[Gráinne]

Hi @Rahul_RVS

Thank you for the warm welcome to the community!

I appreciate your suggestion regarding the Agile Velocity & Status Gadgets app. It sounds like a useful tool for tracking team velocity and productivity. I will definitely take a look at it.

Thank you for the recommendation.

Best regards,
Gráinne

[Humashankar VJ]

Hi @Gráinne 

The native velocity report has limitations when it comes to filtering data by specific sprints or dates.

• The built-in functionality and JQL constraints make it challenging to customize the report without compromising data integrity, particularly when tracking story points across sprints.
• For instance, using 'sprint not in (...)' can remove issues from excluded sprints entirely, spinning velocity calculations for subsequent sprints.
• Moreover, Jira's JQL filters wont support for operators like '>' for sprint numbers or dates.

You can try utilizing third-party add-ons like eazyBI or Custom Reports for Jira, which offer more flexible filtering and visualization options. With eazyBI, you can build custom reports and filter data by sprint names, dates, or other criteria. At the same time, am unsure this option will fully fit your need.

Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards

[Gráinne]

Hi Humashankar,

Thank you for your detailed response. I appreciate the insights regarding the limitations of the native velocity report and JQL constraints. I will explore the third-party add-ons for Jira that you mentioned.

Thanks again for your assistance. Have a great day!

Warm regards,
Gráinne