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!

[Alexey Pavlenko _App Developer_]

Hi @Jon Harry ,

Yes, unfortunately, natively it's impossible to create a multi-project/team sprint report on a dashboard, you will need a 3rd party app for that. This was one of the reasons why I developed Multi-team Metrics & Retrospectives. With it, you can address all your requests.

You can display multiple teams across several periods (sprints/months/quarters/half-years/years) with pre-defined metrics, and additionally create as many custom metrics as you need. Color coding can be applied based on a team or a metric.

Completed vs Remaining Story Points

See Completed Scope and Uncompleted Scope in the Screenshot #1 and #2.

Total story points completed across all active sprints:

See Completed Scope metric in the Screenshot #1.

Velocity across projects

See Averge for Completed Scope metric in the Screenshot #2.

Blockers:

Depends how you determine blockers, but if you just use links for that, the JQL should be:

issueLinkType = "blocks" and issueLinkType != "is blocked by"

Overdue issues:

Choose 'Uncompleted Scope' as an underlying metric. Use this JQL

duedate < now()

Screenshot #1

  

                                                                      ...

Screenshot #2

Best regards,
Alexey

[Manish Nadar]

You can check the usage of Rich Filters in Jira. 

[Joshua Brock _ Seibert Group_ GmbH]

Greetings @Jon Harry ...

Apologies as you're getting some good feedback in rapid succession ;-)

I will add our Jira Cloud plugin solution Agile Hive. Dashboards (PI progress, story points burned, business value, load vs capacity, etc.) dependency management, roadmap and backlog management, completely integrated with your Jira instance.

Any questions, please feel free to reach out!


Joshua
Content & Technical Writer
Agile Hive (Seibert Group, GmbH)

[Mariia_Domska_SaaSJet]

Hi @Jon Harry 

Welcome!

You’re definitely not alone in this — just last week, a similar question inspired me to build a Cross-Project Dashboard using app No-code Apps Creator for Jira, developed by my team.

I tried to solve the challenge:

Create a cross-project status dashboard that shows:
– Project summary cards with overall status
– Charts of issue counts by status
– A milestone timeline
– A list of overdue or blocked issues
– A dropdown to filter by department

If you’re interested, I actually recorded a short video walkthrough showing how I created the Cross-Project Dashboard — happy to share it here if that helps 

https://www.loom.com/share/91381db6519a4ca8b2897f8ea706147d?sid=0bd23b21-60f1-4df1-b0fc-c89cc12f0e61

The best part of using No-code Apps Creator is that all apps and dashboards are built with AI and no coding. You just describe what you want, and it helps you design the dashboard layout and filters.

[Danut M _StonikByte_]

Hi @Jon Harry,

Welcome to the Atlassian Community!

For a quick view of blockers or overdue issues your could use Jira gadgets like Two Dimensional Filter Statistics, Issue Statistics, Filter Results or Pie chart. But unfortunately, Jira does not provide a cross-team burndown or velocity chart, or an easy way to sum-up a field. You will need an app from Atlassian Marketplace for these. 

If you consider using an app, our Great Gadgets app offers all you need for tracking the cross-project / cross-team progress easily & efficiently. 

Here is how:

• Burndown across projects - this can be easily tracked with the Release Burndown Burnup Chart gadget configured with a filter / JQL that returns the issues from your projects and by setting the dates of your release or sprint. 

  It can be also used as a cross-team sprint burndown chart, but in this case you should ensure that the team sprints are aligned (same start date, same duration)

 

• Velocity across projects - this can be easily tracked with the Kanban Velocity gadget configured with a filter / JQL that returns the issues from your projects and by setting the intervals to match your sprints. 

• Total story points completed across all active sprints - the app offers multiple ways to achieve this. I would recommend the Advanced issue Filter Formula gadget in this case configured to calculate and display the SUM of completed and/or remaining Story Points for a JQL that returns issues from all active sprints: sprint IN openSprints(). It can also calculate percentage of completion.
   

• A quick view of blockers or overdue issues -  I would recommend using the Pivot Table & Pivot Chart gadget - one for blockers, one for overdue issues. Comparing with Jira gadgets I mentioned above, this gadget allows you to split data by multiple fields/criteria, can calculate by count, sum of a field, or percentages and can display the result as a table, heatmap table or charts of various types.

For more details and examples on how to track multi-teams projects, see also this article: https://community.atlassian.com/forums/App-Central-articles/How-to-track-scaled-agile-SAFe-projects-in-Jira-with-Great/ba-p/1929694. The app does not require any special configuration (such as data export / sync), everything will be in real time. 

For any questions, feel free to contact our team at support@stonikbyte.com.

Danut. 

[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