Need help to create dashboard in JIRA

Hi  @Deepali Dabholkar ,

Natively, unfortunately, it's not possible. You can accomplish it with Multi-team Scrum Metrics & Retrospectives.

Below is the Chart configured for the Issue Count.

3 boards/teams in the same view, 1 period selected for analysis:

3 boards/teams in the same view, all periods are clicked for average metrics and dynamics:

As for Planned Epics Vs Closed, can you please elaborate on how you determine whether an epic is planned vs closed? There are many ways this can be organized, just 2 of them:

1. By fixVersion? If so, the original fixVersion always stay there even when you move the epic to the next version?
2. By Due/end date? If so, the original due/end date always stay there even when you change the due/end date for the epic?

Best regards,
Alexey | Developer of Multi-team Scrum Metrics & Retrospectives

Hey @Deepali Dabholkar 

You can get most of this with native Jira — the sprint half especially.

Sprint: planned stories vs closed

Since your team doesn't use story points, switch your board's estimation to issue count:

Board settings → Estimation → Estimation statistic = Issue count

With that set, the built-in Velocity Chart (Board → Reports → Velocity) shows exactly what you're describing: the grey Commitment bar is what was planned at sprint start, the green Completed bar is what actually got done — per sprint, counted in issues rather than points.

The Sprint Report gives the same per-sprint breakdown with the list of completed vs. not-completed issues, and it handles scope changes (issues added mid-sprint are flagged separately).

On a dashboard specifically, add the Sprint Health gadget for the active sprint and use saved filters for the rest:

# Planned
sprint = "Sprint 42"

# Closed
sprint = "Sprint 42" AND statusCategory = Done

Pair those filters with the Issue Statistics or Pie Chart gadget grouped by status.

PI: planned epics vs closed

Jira has no native PI concept, so this depends on how you tie epics to a PI — most teams use a fix version or a label. If it's a fix version:

# Planned
issuetype = Epic AND fixVersion = "PI 12"

# Closed
issuetype = Epic AND fixVersion = "PI 12" AND statusCategory = Done

The Two Dimensional Filter Statistics gadget with Fix Version on one axis and Status on the other gives you a planned-vs-closed table per PI right on the dashboard.

The gap you'll hit

The velocity chart lives in board reports rather than on a dashboard, and the native dashboard gadgets mostly produce tables or single-dimension pies — there's no built-in way to put a planned-vs-closed bar chart per sprint or per PI on a dashboard.

If you want that as an actual chart, a Marketplace charting gadget can do it — full disclosure, my team builds one (Pallas Charts) that groups issues by sprint or version and splits them by status category. But try the native route first; for many teams the velocity chart plus a couple of filter gadgets covers it.

Thanks,

Anderson

Hi @Deepali Dabholkar,

Unfortunately Jira doe snot provide such dashboard gadgets. You could eventually try the space report instead.

For having these on a dashboard, you will need to search on Atlassian Marketplace for a plugin (app) that provides such gadgets. 

If you want to try a plugin, our Great Gadgets app offers all you need for building such dashboard.

For Sprint performance I would recommend using the Team Velocity gadget, which shows can show Committed vs Completed, and eventually % Completed, by count of stories and other work items.

 For PI performance, I would recommend  using the Release Burdown Burnup Chart gadget to create a PI burndown chart.

 If you want to measure the epics completion, then use its Pivot Table & Pivot Chart gadget to display the epic progress by their child stories. 

Have also a look over these articles: 

• https://community.atlassian.com/forums/App-Central-articles/8-gadgets-for-a-powerful-Scrum-dashboard-in-Jira/ba-p/1683063
• https://community.atlassian.com/forums/App-Central-articles/How-to-track-scaled-agile-SAFe-projects-in-Jira-with-Great/ba-p/1929694

If you need any help with the configuration of our gadgets, feel free to contact support@stonikbyte.com.

Danut. 

The first step is deciding who the dashboard is for and what questions it should answer. Once you have that, create a saved JQL filter and use it as the data source for your gadgets. 

As some mentioned, your need seems quite standard and can be done with Jira native options, through a report, a dashboard that require a JQL filter to be created, or even inside the Issue view you can see the Epic progress bar as follows:

If you're looking for a different way of visualizing performance and you're open for 3rd party solutions, Millarum Dashboards have plenty of options to customize how to visualize your data. The simplest way to visualize could be as follows for Epics or Sprints

Greetings @Deepali Dabholkar !

For the Sprint Performance dashboard, since your team doesn't allocate story points, set your board's Estimation statistic to Issue count (Board settings → Estimation). The Velocity and Sprint Burndown gadgets will then report Planned vs. Closed as plain issue counts, which is exactly what you're after there.

The PI Performance dashboard is trickier because, as noted, Jira has no native PI concept. Most teams simulate it with a fixVersion or label on the epics (e.g. issuetype = Epic AND fixVersion = "PI-2026.3" for planned, plus AND statusCategory = Done for closed), then put those filters behind an Issue Statistics gadget. It works, but it's a convention you have to rebuild and maintain by hand every PI.

If your organization is running SAFe, or moving toward it, that's the specific gap Agile Hive is built to close: Program Increments and ARTs become real, first-class structures in Jira instead of a fixVersion convention, so this kind of PI reporting comes out of the box. For a single team's PI performance specifically, it includes:

• Team PI Progress reports with velocity and story points (or issue counts) burned vs. planned
• A PI Iterations view showing progress per iteration inside the PI, alongside capacity vs. load
• Team PI Objectives tracked and linked back to the work that delivers them
• Sprint- and PI-level views side by side, without hand-built fixVersion filters

You can see it here on our Marketplace listing.

One honest caveat: the reporting above is strongest at the team and ART level. If you later need those numbers rolled up across multiple ARTs or into a full portfolio view, that's an area still being actively built out, so it's worth checking where that stands before counting on it for higher-level reporting.

Disclosure: I work at Seibert Group GmbH, the team behind Agile Hive.

Hope this helps!

Joshua
Content Writer & US Representative
Agile Hive and Aura Apps (products of Seibert Group GmbH)

Hi @Deepali Dabholkar ,

You don't actually need story points for either of these — both work fine with issue counts.

Sprint: Planned vs Closed stories. Set your board's estimation statistic to Issue count (Board settings → Estimation). The Velocity Chart on the board then shows Commitment vs Completed per sprint as plain issue counts — that's exactly planned vs closed. On a dashboard, the Sprint Burndown gadget follows the same statistic.

One caveat: "commitment" is the scope at sprint start, so mid-sprint additions show up as scope change rather than inflating the planned number.

PI: Planned vs Closed epics. Jira has no native PI entity, so the first step is marking which epics belong to a PI — most teams use a fix version (e.g. PI-2026.3) or a label on the epics. Then two saved filters drive it:

• Planned: issuetype = Epic AND fixVersion = "PI-2026.3"
• Closed: same + AND statusCategory = Done

Put those behind Issue Statistics (grouped by status) or Two Dimensional Filter Statistics gadgets and you have your planned-vs-closed view. Advanced Roadmaps (Premium) helps with the planning side but still won't give you this as a dashboard chart.

Full disclosure — I'm the developer of Plugio Suite, so take this part with that in mind: if the native gadgets feel too rigid for the PI view, the suite's metrics are count-based by default (no estimates needed anywhere), and you can scope a whole dashboard to that PI fix version and count epics by status however you like — single numbers, pie, bar, or a pivot table. It also has sprint-based dashboards that stay bound to your scrum board's active sprint for the sprint view.

Hi @Deepali Dabholkar 

Welcome to the Atlassian Community!

FYI, Jira offers several built-in reports under the Reports section. I believe Sprint Report, Epic Report are already available along with many other reports.

Cheers!

P.S. If you'd like to create dashboards, you can build them using saved filters. For example, create a filter such as Project = TEST AND issuetype = Story AND Sprint = "Sprint 123" and then use that filter in a Pie Chart gadget, with Status selected as the statistic type