Jira Reporting for Product Managers: Charts, Metrics, and Dashboards
Product managers and engineering teams look at the same Jira data and need different things from it. Engineering wants sprint health, cycle time and blocked issue counts. Product management wants feature progress, release readiness, customer-reported bug trends, and backlog composition.
Most Jira dashboards are set up by or for engineering teams. If you're a PM who has tried to get useful reporting out of Jira and ended up with a page full of gadgets that don't answer your actual questions, this guide is for you.
The Four Questions a PM Dashboard Should Answer
Before picking any chart, start with the questions:
- What's the state of the current release? Feature completion, open bugs, scope changes.
- What's the trend for customer-reported issues? Bug volume over time, resolution rate.
- What does the backlog look like? Priority distribution, backlog by product area.
- What shipped recently? Completed features, closed bugs, material for release notes.
If your dashboard can answer these four questions without anyone opening a filter or running a query, it's doing its job. The charts below use Charts - Reports and Graphs for Jira Dashboard, a free dashboard gadget, alongside a couple of Jira's built-in gadgets.
Chart 1: Release progress
The question: How far along are we in the current release?
Setup:
- Chart type: Bar (stacked)
- Scope (JQL):
fixVersion = "Your Release Name" - Group by: Status
A stacked bar with a segment per status (To Do, In Progress, In Review, Done) shows at a glance how much is done, how much is in flight and how much hasn't started. When the Done segment is 80% or more of the bar with a week left in the release, you're in good shape. When To Do still represents 40% with the release date looming, you have a scope problem.
JQL filter:
project = YOURPROJECT AND fixVersion = "v2.4" AND issueType in (Story, Bug, Task)
Chart 2: Customer-reported bug trend
The question: Is the volume of customer-reported bugs stable, rising or falling?
Setup:
- Gadget: Jira's built-in Created vs Resolved gadget
- Filter: a saved filter such as
labels = customer-reported AND issuetype = Bug(or however your team tags customer bugs) - Period: daily or weekly, over the last 90 days
Created vs Resolved shows incoming bugs against fixed bugs over time, which is exactly the trend a PM needs. A stable picture means quality is consistent. A rise in created bugs after a release points to regressions. A falling line is good news, though it's worth confirming it isn't just a drop in reporting.
To see where today's open customer bugs sit, add a Charts for Jira bar chart with the same filter, grouped by priority or status.
If your team doesn't use a consistent label for customer-reported issues, now is a good time to start. The reporting value is significant.
Chart 3: Feature vs. bug ratio in the backlog
The question: Is the backlog dominated by one type of work?
Setup:
- Chart type: Pie (donut style)
- Scope: Open issues in the project
- Group by: Issue type
For a product team, the ideal ratio depends on the product maturity stage. A new product might be 80% features and 20% bugs. A mature product with a large install base might be 50/50. What you're watching for is a trend. If the bug proportion grows every quarter, quality investment is falling behind.
This is also useful for product strategy conversations: when engineering says they need a "bug bash sprint," this chart gives you the data to support (or challenge) the request.
Chart 4: Backlog by priority
The question: How much of the backlog is urgent?
Setup:
- Chart type: Bar (horizontal)
- Scope: Open issues in the backlog
- Group by: Priority
A priority bar chart shows how the backlog breaks down by Critical, High, Medium, and Low. The ratio matters: a backlog that's 30% Critical and 40% High is telling you that your priority labels have inflated to the point of meaninglessness, or that there's genuinely too much urgent work and the team can't keep up.
Review this chart before each quarterly planning cycle. If the High bar keeps growing despite the team working on High-priority issues, capacity is mismatched with demand.
Chart 5: Completed work by area
The question: What shipped this quarter, and in which product areas?
Setup:
- Chart type: Bar
- Scope (JQL):
statusCategory = Done AND resolved >= -90d - Group by: Labels (product area labels)
This chart is a retrospective view of where the team's output went. If you have labels for product areas ("auth," "billing," "reporting," "mobile"), a bar chart of completed issues by label shows what got attention. It's a useful starting point for "was this the quarter we said we'd focus on X?" conversations.
It also helps with release notes: scope it to the release's fixVersion and group by issue type to see what categories of work shipped in that release.
Setting Up the PM Dashboard
Create a dedicated Jira dashboard for product management. Don't reuse the sprint team's dashboard. The audiences and review cadences are different.
Recommended layout, three columns:
| Left column | Center column | Right column |
|---|---|---|
| Release progress (stacked bar) | Customer bug trend (Created vs Resolved) | Backlog by priority (bar) |
| Feature vs. bug ratio (pie) | Completed by area (bar) | (optional: Filter Results for escalations) |
Each gadget keeps its own scope, so when the release or quarter changes, update the fix version or date in each chart's JQL (saved filters make this a one-place change).
Share it: Share the dashboard with the engineering manager, design leads and anyone who prepares leadership updates. A shared dashboard replaces the "can you pull the Jira report for the leadership update?" request with a link they can check themselves.
What Good Jira Reporting Looks Like
The sign that your dashboard is working: you open it in a meeting, look at it for 30 seconds, and can answer questions from it without typing a single JQL query. If you're still exporting to spreadsheet to get the answer you need, the dashboard isn't answering the right questions yet.
Start with the release progress chart and the bug trend. Those two alone are more valuable than most Jira dashboards that have eight gadgets.
For more chart setups, see How to Track Jira Issues with Charts and Graphs, and for the built-in gadgets that pair well with them, Best Jira Dashboard Widgets and Charts in 2026.
