Tagline: Pivot tables, charts and time-in-status over any JQL — live, timezone-correct, and a third of the price.
Getting started
1. Install
Install from the Marketplace listing, or in Jira go to Apps → Explore more apps and search for Pivot Reports for Jira. You need to be a Jira administrator. There is nothing to configure before first use.
2. Build your first report
Open a project and go to Project menu → Apps → Pivot Reports for Jira.
Under Source, choose the project or paste a JQL query.
Under Rows, pick the field to group by — assignee, status, issue type, a label, any custom field.
Under Columns, optionally pick a second field, or a date field with a bucket (day, ISO week, month, quarter, year).
Under Measures, choose what to count: Issue count, or a sum, average, minimum or maximum of any numeric field, cycle time, or age.
The table draws as you go, with subtotals and a grand total. Click any number to drill through to the work items behind it.
3. Chart it, export it, save it
Chart — under Display, switch Show as from Value to Chart and pick a chart type.
Export — choose Export for a CSV, or a picture of the report. CSV values are escaped so a spreadsheet cannot execute them.
Save — choose Save report to keep the definition. Saved reports are private to you unless you share them with the project.
4. Report on history
Under Issue history, set an As of date to rebuild every work item's fields as they were at the end of that day, leaving out items created later. For a time-in-status report, choose Status (time in status) as the rows field and Days in status as the measure. History reports read a changelog per work item, so they are limited to 1,500 items.
5. Put a report on a dashboard
Save the report first.
Go to Dashboards, edit a dashboard, choose Add gadget and search for Pivot Report.
Edit the gadget and pick the saved report.
If something looks wrong
Numbers look lower than expected. Reports run as the signed-in person, so each viewer only sees work they already have permission to see. Two people can legitimately see different totals.
A custom field is missing from the list. Only fields available to the projects in your source query appear. Widen the source, or check the field's context in Jira.
A history report is truncated. That is the 1,500-item limit above; narrow the JQL.
Summary
Pivot Reports turns a JQL query, a board, a sprint or a saved filter into a pivot
table and a chart in three clicks: pick a row field, an optional column field, and one
or more measures. Count issues, sum or average story points, time spent, estimates or
any number field, take a median or an 85th percentile, or write a small formula like
sum(points) / count — broken down by status, assignee, priority, type, epic, sprint,
version, component, label, any select/user/date custom field, or by created/resolved
date per day, week, month, quarter or year. Every cell drills down to the issues
behind it.
Ask how long work actually sits in each status, or what the board looked like on a
date three months ago, and get an answer read live from Jira's own change history —
no import, no cube, no query language to learn. The app reads Jira as you, so what you
see is exactly what your permissions allow, and nothing leaves Atlassian's
infrastructure (Runs on Atlassian).
Highlights
Any two fields, any measures. Rows × columns pivot with row subtotals, column
totals and a grand total that always reconcile. Up to six measures side by side:
count, sum, average, min, max, median, 75th/85th/90th/95th percentile.
Calculated measures. A small, safe formula language over those aggregations —
sum(customfield_10016) / count, count - sum(x). Evaluated from each cell's own
totals, so a subtotal is the true weighted figure, never an average of averages. No
MDX, nothing to execute, nothing to hire a consultant for.
Time in status. How long each issue spent in each status, from the changelog,
with percentiles and an optional window. Durations always reconcile with the issue's
own age, at every level of the table.
As of a date. Rebuild the report as it stood at the end of any past day — status,
assignee, priority, labels, components, versions, story points — from each issue's
history, in your timezone. Issues created later are left out.
Percent views. Any report as % of total, % of row or % of column.
Time buckets that are actually right. Dates are bucketed in your Jira timezone,
not the server's, by day, ISO week, month, quarter or year — including across
daylight-saving changes.
Fifteen chart types. Bar, grouped bar, stacked bar, 100% stacked, horizontal bar,
horizontal stacked, line, area, pie, donut, funnel, tile, gauge, table, and a table
heat map — drawn with Atlassian's own components, so they match your Jira theme.
Conditional formatting. Colour cells by thresholds you set, or a heat map fitted
to the numbers on screen. Follows light and dark themes.
Cross-project. Report on one project from its page, or across every project you
can see, with one checkbox.
Sources beyond JQL. A board, a sprint, a saved filter or a JQL query — and any of
them narrowed further by your own JQL.
Quick filters. Define named filters on a report; readers pick one on the page or
on a dashboard to narrow it. A quick filter can only ever narrow, never widen.
Curate the values. Rename values (two renamed alike read as one row), hide the
ones you do not want, and pin the order that matters.
Drill-down. Click any cell, subtotal or total to list the issues in it.
Saved reports, in folders. Keep reports private, or share them with everyone who
can browse the project — or only with chosen project roles. Every check runs on the
server, on every open.
Dashboard gadget. Put any saved or ad-hoc report on a Jira dashboard, quick
filters and all.
Export. CSV with RFC 4180 quoting and formula-injection protection, and PNG or
PDF of the table and chart together.
Scheduled snapshots. A project admin can have a shared report refreshed daily and,
if they choose, have Jira notify the report's audience.
Complete data. The JQL is paged to exhaustion (up to 5,000 issues per report,
1,500 for reports that read history) with a clear warning when a query exceeds that —
never just the first page.
Almost entirely read-only. Scopes: read:jira-work, read:jira-user,
storage:app, and write:jira-work used for exactly one thing — asking Jira to send
the optional scheduled notification. The app never creates, edits, transitions,
comments on or deletes an issue.
What it is not
Pivot Reports is the deterministic core of a BI tool, not a data warehouse. It does not
import your data into a cube, has no MDX, does not join other data sources (SQL,
Google Sheets, Tempo), and cannot publish a report to the public web. If you need
those, eazyBI is the right tool — at its price. See COMPETITORS.md for the full
comparison, including what is impossible for an app that never sends your data
anywhere.
Pricing
US$3 a month flat for up to 10 users, then US$1.00 per user per month, flat.
Annual billing: 10 months for 12.
Why: the two apps most teams use for this cost about three times as much per user at
the sizes most teams are. Both are good tools that most customers use for exactly what
Pivot Reports does — count and sum issues by a field or two, chart it, put it on a
dashboard, and ask how long things sat in a status. A 50-person site pays about $150 a
month for either incumbent and $50 here; a 10-person team pays $3.
Support
Documentation and support: to be published with the Marketplace listing.