Jira Reports for Managers: Throughput, Backlog and Bugs
Turn Jira issues into a weekly report managers read: throughput, backlog, bug trends and workload, the JQL filters to use and what Jira data cannot tell you.
· 4 min read · Summarix team
Managers rarely need another Jira board; they need a short report that says how much work got done, what is piling up, whether bugs are rising and who is overloaded. You can produce one from Jira's own issue data: filter the issues with JQL, count them by status, priority, type and assignee, and chart created and resolved issues by month. Keep one filter per question, and say plainly what the data cannot show.
What comes across from Jira
Summarix connects to Jira Cloud with your site (yourcompany.atlassian.net), an account email, an API token and an optional JQL filter. Without a filter it imports issues created in the last 365 days. Each issue becomes one row with these fields:
| Fields | Good for |
|---|---|
| key, summary | Identifying issues in tables and lists |
| status, priority, issuetype, project | Breakdowns: open work by status, bugs by priority, issues by project |
| assignee, reporter | Workload and who raises the most issues |
| labels | Themes, if your team labels consistently |
| created, updated, resolutiondate, duedate | Trends by month: created versus resolved, and when work is due |
You choose how often it syncs: manually, every hour, daily or weekly. Each sync refreshes the same dataset, up to 200,000 issues, so a scheduled report always uses the latest sync. The API token is stored encrypted, and it can see exactly what its Jira account can see, so create it from an account with read access to the projects you want to report on and nothing more.
Write the JQL first
Summarix's KPIs are calculated over the whole dataset, so the filter is where you decide what the report is about. A focused filter gives a focused report. A few that work well:
project = OPS AND created >= -90d
project in (WEB, APP) AND resolved >= -28d
issuetype = Bug AND created >= -180d
project = OPS AND statusCategory != Done
duedate < now() AND statusCategory != DoneThe last one is worth its own connection: Jira works out 'overdue' for you, so a dataset of overdue issues counts exactly what you want. Because each connection is one filter, it is normal to have two or three Jira connections, each answering one question.
Five measures managers actually use
| Measure | How to get it | What it tells you |
|---|---|---|
| Throughput | Issues resolved, charted by resolutiondate (grouped by month) | Whether delivery is steady, rising or falling |
| Created vs resolved | Count by created and by resolutiondate, side by side | Whether the backlog is growing |
| Open backlog | A filter on unresolved issues, counted by status and priority | Where work is stuck |
| Bug trend | A filter on issuetype = Bug, counted by created month and priority | Whether quality is improving |
| Workload | Open issues counted by assignee | Who is overloaded, and who is free |
What Jira data cannot tell you here
Be honest about the limits, so nobody reads more into the report than it holds:
- Cycle time: the time between created and resolved needs a calculation between two dates. Summarix aggregates columns as they are, so use Jira's own control chart, or export issues with a calculated column and upload the file.
- Story points and time tracking: these live in custom or time-tracking fields that are not part of the import.
- Status history: the import has the current status, not how long an issue sat in each one.
- Effort: a count of issues treats a two-minute fix and a two-week feature the same. Read throughput as a trend, not a productivity score.
Building the weekly report
- Under Integrations, connect Jira with a JQL filter for the question, and set it to sync daily.
- Generate a report from the new dataset with a focus such as For the Monday delivery meeting: issues by status and priority, open issues by assignee, created and resolved by month, and any high-priority issue still open. See how to brief an AI report.
- Read the build log and the data-quality notes the first time: blank assignees and unused priorities show up there.
- On a paid plan, add a schedule: weekly, Monday, at an hour after the morning sync, with the meeting attendees as recipients.
- Optionally connect a Slack or Microsoft Teams channel, so the summary is posted when the report is ready.
For more on timing schedules around syncs, read keeping report data fresh. If you are still deciding which measures belong in the report, start with operations KPIs and how to choose KPIs.
Connect Jira, pick a filter and get a weekly delivery report your managers will actually read.
Free plan: 5 AI reports a month, no card needed.
Frequently asked questions
Does Summarix work with Jira Server or Data Center?
The connector is for Jira Cloud sites (yourcompany.atlassian.net). For a self-hosted Jira, export issues to CSV or Excel and upload the file, or send rows from an automation tool to a push URL.
Can I report on several projects at once?
Yes. Use a JQL filter such as project in (WEB, APP), and break the numbers down by project in the report. Keep separate connections if the projects have very different workflows.
Is the Jira API token safe to give?
It is stored encrypted, and it only has the access of the Jira account that created it. Use an account that can read the projects you report on, and revoke the token in Atlassian if you remove the connection.
Why does my report show issues from last year?
Without a JQL filter, the import covers issues created in the last 365 days. Add a filter such as created >= -90d, or resolved >= -28d for recent throughput, so the report covers the period you want.