Is there a way to adjust the Timeframe range on a Velocity Report?

Question

We recently migrated to Jira Cloud from Data Center.  Is there functionality in Jira Cloud that allows you to adjust the timeframe range on a Velocity Report?  As of now, you see all sprints (up to 120) but users are wanting to only see sprints for a specific period of time.

Andrey - Guenov Labs · Answer

Hi Maggie, welcome to the Community.

Short answer: no — the Velocity Chart in Jira Cloud has no timeframe control of its own. There's no date range, no "last N sprints" setting, and nothing in the board's report configuration that narrows it. That's a real difference from what you're used to on Data Center, and it isn't something you've missed in the migration.

What's worth knowing is why, because it points at the only lever you have. The Velocity Chart doesn't have a scope of its own at all — it renders every closed sprint associated with the board, and which sprints those are is determined entirely by the board's filter. So the setting you're looking for doesn't live in the report; it lives in the board.

That gives you a practical workaround: clone the board and narrow the clone's filter so only the period you care about is in scope. Something like adding AND sprint in openSprints() OR sprint in closedSprints() won't help on its own, but constraining the underlying work — e.g. project = ABC AND created >= "2026-01-01", or scoping to a component/team that only existed in that window — reduces which sprints have matching issues, and therefore which sprints appear on the chart. It's blunt, and it's worth testing on a copy before you point anyone at it, but it's the only native lever.

If you need an exact rolling window (last 6 sprints, or a specific date range), the Agile REST API gives it to you cleanly:

* GET /rest/agile/1.0/board/{boardId}/sprint?state=closed — returns each sprint with startDate/endDate, so you can select exactly the ones in your period
* GET /rest/agile/1.0/sprint/{sprintId}/issue — returns the issues per sprint, including estimates

Twenty lines of script, or a scheduled Automation rule writing to a page, and you have a velocity series over any window you like — and you can compute committed-vs-completed properly, which the built-in chart handles but doesn't let you export.

One practice note, offered as opinion rather than an answer: if your users are looking at 120 sprints of velocity, the chart is arguably already failing them regardless of the date filter. Velocity is a rolling-average instrument — most teams read the last 3–6 sprints and treat anything older as a different team with the same name. If what they actually want is "are we going faster or slower than a quarter ago," a scoped board showing the recent window will serve them better than a date picker on the full history would.

If you'd find the filter genuinely useful as a product feature, jira.atlassian.com is the place to raise or vote on it — DC-to-Cloud reporting gaps get real attention there when they're documented with a concrete use case like yours.

Danut M _StonikByte_ · Answer

Hi @Maggie Rhoads,

Welcome to the Atlassian Community.

The Velocity Report in Jira Cloud does not offer the option to filter the displayed sprints by date range.

I see no workaround for this, other than looking for a plugin (app) on Atlassian Marketplace that offers sprint date filtering capabilities.

If you are open to using an app, our Great Gadgets app offers a Team Velocity Chart gadget that displays the data available in Jira's Velocity Report, along with many other useful sprint metrics, such as scope change, completion percentage, and more.

It also allows you to filter the sprints to be displayed by various criteria, including a specific date range.

You can find more about this gadget in this article: https://community.atlassian.com/forums/App-Central-articles/9-gadgets-for-a-powerful-Scrum-dashboard-in-Jira/ba-p/1683063

Danut.

Rustem Shiriiazdanov _Actonic_ · Answer

Hi Maggie,

TLDR: no, you’re not missing a setting. Jira Cloud’s Velocity Chart currently doesn’t have a timeframe control, but since you are in Enterprise plan, you may consider using Analytics to create a custom report.

Long read: This is one of the differences from Data Center. In Jira DC, the Velocity Chart lets you choose a predefined timeframe or a custom date range. In Cloud, the report is board-specific, but there’s no equivalent control for “last N sprints” or a date range. There’s also JRACLOUD-90457 [JRACLOUD-90457] As a Product Owner, I want to be able to define the number of sprints to be disabled in Velocity Chart - Create and track feature requests for Atlassian products. asking for a configurable number of sprints, but that’s still open. Vote for it to get Atlassian attention for the issue :)

Cloud also doesn’t have the Focus or Save as image controls available in Data Center, so even the “just crop the relevant sprints for the slide deck” workaround isn’t really there. The board’s saved filter is basically the only lever, and it doesn’t filter the chart by time.

I see that you have an ENTERPRISE product planm, so you also have Atlassian Analytics. You can build a velocity view there with whatever date range you need. That’s probably the closest native answer. The trade-off is that it’s more of a BI solution, but If you’re already using Analytics, though, it’s definitely worth considering.

If using the Analytics is not your way, I, as a marketplace vendor, may suggest you considering marketplace apps such as the one my team has developed - Report Builder for Jira https://marketplace.atlassian.com/apps/1216997/report-builder-custom-charts-dashboards-for-jira?hosting=cloud&tab=overview

Our Sprint velocity template gives you the control that’s missing from the native Cloud report:

* choose the last N closed sprints, or display all closed sprints;
* optionally include active and future sprints;
* calculate by story points, work item count, or time;
* show average and trend lines;
* put the report on a Jira dashboard as a gadget.

It’s also a scripted report, so after saving the template you can edit its JavaScript/HTML. For example, if your stakeholders think in quarters rather than “last 6 sprints”, you can replace the last-N logic with a start/end date based on the sprint completion date.

Hope this helps