How Can I Create a Dashboard That Tracks Sprint Progress Across Multiple Projects in Jira Cloud?

[Jon Harry]

I’m trying to create a Jira dashboard that shows sprint progress (completed vs remaining story points) across multiple Scrum projects in Jira Cloud.

Right now, each project team runs their own sprints, but management wants a single overview dashboard to see:

• Total story points completed across all active sprints

• Burndown or velocity across projects

• A quick view of blockers or overdue issues

I’ve tried using:

• The Filter Results gadget with a JQL query (e.g., Sprint in openSprints())

• The Sprint Burndown gadget, but it only works for one project at a time

Is there a way to combine multiple projects into one sprint view or burndown chart in Jira Cloud? Or do I need a Marketplace app (like eazyBI or Custom Charts)?

Would appreciate any best practices or setup ideas!

[Mary from Planyway]

@Jon Harry 

While Jira's native sprint gadgets are project-specific, achieving a multi-project sprint overview is definitely possible, though it often requires a combination of strategies.

Enhanced JQL with Filter Results Gadget (for basic metrics):
You're on the right track with the Filter Results gadget. While Sprint in openSprints() is good, you can create more powerful filters for specific data points.

• Total Story Points Completed:
  You can write JQL to find all issues completed in any active sprint across your desired projects.

  codeJql

  statusCategory = "Done" AND issuetype = "Story" AND resolutiondate >= startOfMonth() AND project in ("Project A", "Project B", "Project C") AND sprint in openSprints()

  This filter shows what has been done. To get story points, you'd then need to sum the "Story Points" field from the results. The Filter Results gadget will list issues, and you can display the "Story Points" column, but it won't sum them directly for you. You'd have to manually sum them or export to a spreadsheet.

• Blockers/Overdue Issues:
  This is more straightforward with JQL.

  
  

  (statusCategory != "Done" AND duedate <= now() AND duedate is not EMPTY) OR (status = "Blocked" AND statusCategory != "Done") AND project in ("Project A", "Project B", "Project C") AND sprint in openSprints() ORDER BY duedate ASC

  Display this in a Filter Results gadget.

Native gadgets struggle with aggregation (like summing story points or calculating velocity) across multiple projects in a single view. Burndown charts are strictly single-project.

Planyway Plugin for Jira 

If you try Planyway plugin, this can offer a powerful solution for multi-team planning and progress tracking.

• Capacity Planning & Roll-up: You can define your teams, assign them to projects, and plan work across multiple sprints and projects.

• Reporting: It has its own reporting capabilities that can show progress against plans, though it's more focused on roadmapping and time tracking than granular sprint burndown. You can see planned vs. actual progress and identify dependencies.

• Visualization: It provides timeline views that can give you an idea of overall progress.

Best for: High-level strategic overview, dependency tracking, and future planning across multiple teams/projects . Less ideal for a detailed, aggregate sprint burndown.

eazyBI

eazyBI is a business intelligence app that pulls data from Jira (and other sources) and allows you to build highly customized reports, charts, and dashboards using a drag-and-drop interface and MDX queries.

• Multi-Project Burndown/Velocity: You can absolutely create burndown charts that aggregate data from multiple sprints across different projects into a single view. You can track "Story Points Completed," "Remaining Story Points," and calculate velocity across any combination of teams/sprints .

• Custom Metrics: Easily define your own metrics (e.g., "Average Velocity Last 3 Sprints for All Teams").

• Blocker/Overdue Insights: While JQL can list them, eazyBI can create trend reports, show counts over time, or even calculate the average time issues spend in "Blocked" status across projects.

Custom Charts for Jira

Custom Charts is specifically designed to create beautiful, interactive, and highly configurable charts for Jira dashboards. It's often more intuitive for pure dashboard visualization than eazyBI for many common scenarios. Your Use

• Multi-Project Sprint Progress: You can create charts that show "Story Points Completed" vs. "Remaining" across multiple projects.
• Velocity Charts: Easily build velocity charts that aggregate data from selected sprints across different projects.

Jira Misc Workflow Extensions (JMWE) or ScriptRunner 

While not dashboard apps, these can help prepare your data if you're trying to stretch native Jira's capabilities. For example, you could theoretically create a custom field that aggregates sprint data in a very specific way, but this gets complex quickly and is generally not recommended for dashboarding aggregated metrics like burndown.

[Matteo Vecchiato]

Hi @Jon Harry ,.

Thank you for your post.

Based on my experience, it is possible with Eazybi. You can find example of Agile reports in this Eazybi demo site: https://eazybi.com/accounts/1000/dashboards/16272-agile  

Regards