Partly. Jira’s filter-based gadgets — Filter Results, Two-Dimensional Filter Statistics, Work Item Statistics — already aggregate across projects today, because they run on a JQL filter and JQL was never scoped to one project. What doesn’t cross projects is the sprint part: Sprint Burndown, Sprint Health, and Days Remaining in Sprint are all built around a single sprint on a single board, so there’s no native way to put multi-project sprint progress on one chart — unless you’re on Jira’s Enterprise plan, which ships exactly one template built to do it. That split — counts aggregate fine, sprint metrics don’t — is the whole shape of this question, and it’s why search results for “dashboard across multiple projects” feel contradictory: some answers are right about the filter gadgets and wrong about sprints.
What already works: filter-based gadgets
Jira’s own dashboard gadget documentation lists three gadgets that run on a saved filter rather than a fixed project: Filter Results (a live issue list), Two-Dimensional Filter Statistics (a breakdown table across two fields), and Work Item Statistics (issues grouped by one field). None of the three is restricted to a single project — they inherit whatever scope the underlying JQL filter has. So a saved filter like:
project in (WEB, MOBILE, INFRA) AND sprint in openSprints()feeds any of those gadgets a real cross-project view: status counts, a breakdown by assignee, a table of priority × project. Atlassian’s own steps for adding gadgets are the standard entry point — create a dashboard, add the gadget, point it at the saved filter. This part of “cross-project dashboard” is solved, has been for years, and doesn’t need a plugin.
What doesn’t: sprint burndown, velocity, and health
The gap is specifically the sprint-shaped gadgets. Per the same gadget documentation, Sprint Burndown, Sprint Health, and Days Remaining in Sprint are all configured against one sprint at a time — and a sprint belongs to one board, which is normally scoped to one project. There’s no equivalent “Multi-Project Sprint Burndown” gadget in the native set. If what you actually want is “how much of this quarter’s committed work, across three teams’ sprints, is actually done” as one chart, none of Jira’s built-in sprint gadgets get you there, no matter how the underlying JQL filter is written — burndown and velocity math isn’t filter-driven the way a status count is.
This is exactly the question asked, in almost these words, in “How Can I Create a Dashboard That Tracks Sprint Progress Across Multiple Projects in Jira Cloud?” — 5,333 views and 9 answers at the time of writing. The asker wanted total story points completed across active sprints, burndown/velocity tracking, and blocker visibility, and noted plainly that “native Sprint Burndown gadgets only work for single projects.” The thread’s own answers confirm the split above: one response walks through the cross-project JQL-filter approach for counts, and several others say that anything closer to real cross-team velocity or burndown needs a Marketplace app — eazyBI’s cross-sprint burndown charts, Great Gadgets’ Release Burndown/Burnup gadget, and Multi-team Metrics & Retrospectives were all named.
Does the 2026 Summer Release change this?
No — checked directly against Atlassian’s own release announcement, which doesn’t mention dashboards or gadgets anywhere. What it shipped is a merged List view with “full parent/child hierarchy” and new formula fields that calculate values within a single work item. Both are real upgrades, and both are the wrong surface for this question: List view is a work-item list with grouping, not a dashboard, and formula fields explicitly can’t reach across issues (the boundary we go through in detail on summing story points from children to a parent). Neither one touches gadgets, and neither adds a cross-project sprint chart. A Jira Cloud dashboard built today has the same gadget set — and the same sprint-scoped gap — it had before the Summer 2026 release.
The one native answer that does exist — and its price
There is exactly one Atlassian-built dashboard that does what the community thread above was asking for. Atlassian Analytics’ “Multiple Sprints Overview” template ships with a Projects picker specifically so “this dashboard should focus on” more than one software project, and reports committed vs. completed work, scope changes, carryover, and workload per assignee — measured as issue counts, story points, or time, across every selected project’s sprints at once. That’s a genuine, purpose-built answer to “sprint progress across multiple projects,” not a workaround.
The catch is access. Atlassian Analytics ships as part of the Enterprise plan — quoted and sold separately from Standard and Premium, Atlassian’s most expensive and most heavily negotiated tier. Most teams asking this question, including the one in the community thread above, aren’t on it. So the honest state of native Jira is: the exact dashboard exists, and it’s priced out of reach of the majority of people searching for it.
What teams build instead
Two real routes, both visible in the community thread and elsewhere:
- DIY with native gadgets. A saved cross-project JQL filter feeding Filter Results and Two-Dimensional Filter Statistics gets you counts, breakdowns, and status splits across projects — free, native, and genuinely useful, but it stops at counts. It doesn’t produce a burndown or a velocity trend. A Planyway-authored Community article walks through this exact build (
project in ("Project A", "Project B", "Marketing Launch")feeding a mix of native gadgets), and is upfront that the result is a “static snapshot” — no drag-and-drop, no cross-project dependency view — before pointing readers at its own paid roadmap tool for that. - A Marketplace app. eazyBI, Great Gadgets, and Multi-team Metrics & Retrospectives were the three named directly in the community thread, each purpose-built to compute burndown or velocity across sprints from more than one board. All three are separate purchases, separate configuration, and separate things to keep working as your project structure changes.
The honest summary
| What you want | Native Jira | Real option |
|---|---|---|
| Issue counts / status / priority across projects | Filter Results, Two-Dimensional Filter Statistics, Work Item Statistics — free, works today | Built in |
| Sprint burndown or velocity across projects | No native gadget | Enterprise’s Atlassian Analytics template, or a Marketplace app |
| A cross-project view without an Enterprise seat or a plugin | No | Build it yourself from a filter, or a tool built to read the same data |
If your search brought you here expecting a checkbox on a dashboard settings page, there isn’t one below Enterprise — the counts gadgets are free and real, the sprint gadgets stop at one board, and the one template that does both is a tier most teams don’t buy.
What OneView does instead
OneView signs in with your real Atlassian account and reads every project — and every connected site — you can access, without a JQL filter to rebuild per view or an Enterprise plan to unlock the aggregation. You group and roll it up yourself: status, assignee, sprint, or any column you add, spanning as many projects as your work actually touches. It’s the same shape Atlassian Analytics’ Enterprise-only template gives you, without the tier requirement. Start a free trial and point it at your own projects.
Related reading
This page is about the sprint-progress half of “dashboard across multiple projects.” If what you actually need is your own tickets rolled up rather than a team dashboard, see all my Jira tickets across projects — that half is already solved natively, and the harder wall there is a second Atlassian site, not a second project. If what the dashboard is missing is per-person load rather than sprint status — who on the team is actually overloaded, across every project they’re in — that’s a different native gap, covered in Jira capacity planning across projects. If the numbers on a dashboard don’t add up because a parent’s Story Points field isn’t summing its children, that’s a different gap covered in summing story points from children to a parent. And if your projects span two separate Atlassian sites rather than two projects on one site, the dashboard question changes entirely — see a Jira report across two sites.
The same shape shows up on the Microsoft side too: Planner’s Charts view is a real per-plan dashboard with status, bucket, priority, and per-member breakdowns, but — like Jira’s sprint gadgets — it stops at the edge of one container. We cover that gap, and how Team Workload closes it, in a Planner dashboard across all plans. And if the “hierarchy” upgrade you read about in the Summer 2026 release actually solved your problem, check the surface it landed on first — it’s List view, not the Backlog, which still only nests sub-tasks; see parent/child hierarchy in the Jira Backlog.