Docs

Using Roll-up Reports

Pivot tables over your Jira issues, in plain words: pick the issues, choose what to group by and what to show.

Getting started

Install it
From the Atlassian Marketplace, by a Jira admin. It's free for sites with up to 10 users, and bigger sites start with a 30-day trial.
Open it
In Jira, choose Apps → Roll-up Reports. You'll see the report library.
Start from a ready-made report
Choose New report, then one of: Epic progress (open epics with their stories and sub-tasks rolled up), Worklogs by person (time logged in the last 30 days, by person and week), Time in status by team (how long resolved issues spent in progress and waiting), Sprint capacity (estimates and remaining work in the open sprint), or a blank report. It opens on your most active project; change it in the left panel.
Save it
Reports are private until you share them. Every change can be undone (Ctrl+Z or ⌘Z) and redone.

Where to find it

Apps → Roll-up Reports: the library of every report you can see, and the builder.
A project's sidebar → Roll-up Reports: the reports for that project, and new reports that start on it.
A board's ••• menu → Roll-up report: a report of that board's issues, for its open sprint, its backlog or all of it.
Dashboards → Add gadget → Roll-up report: one tab of a saved report, as a chart, a table or both.
Jira settings → Apps → Roll-up Reports: the admin page (Jira admins).

Choose the issues

The left panel, Issues from, says where a report's issues come from:

Project, Board (its open sprint, backlog or all issues), or a saved Filter.
JQL: any Jira query. Its ORDER BY is ignored: the report sorts its own rows.
Keys: a list of issue keys.
Include child issues adds the stories and sub-tasks under what's found, up to three levels down, so epics roll up everything below them.

Reports run as you: they show only the issues Jira lets you see. Big sources load in steps, and the table fills in as they arrive.

Group, show and filter

Group rows by up to four fields, each level inside the one above, with subtotals. Dates group by day, week, month, quarter or year; numbers into ranges; issues with several values (labels, components, sprints) count in each of their values, or in the first only. An issue's first sprint is the one it's in now.
Hierarchy (as the only row grouping) shows each issue under its parent, as a tree.
Columns split each row by up to two more fields.
Show up to 12 values (next section).
Filter by up to 10 fields: values in or not in a list, empty or not, between two numbers or dates, or the last N days. Filters apply straight away, without asking Jira again.
Each grouping can show only the top N groups; the rest are added up in one "Other" row. An issue in several of those groups counts once in Other.
Move chips with the mouse, or with Alt and the arrow keys. Delete or Backspace removes one.

Choose a cell to see the issues behind it, open them in Jira, or open the same list in Jira search.

Values

Counts	Issues, issues with a value in a field, or the number of different values (for example, different people).
Numbers and estimates	Total, average, highest, lowest or weighted average of any number field: original and remaining estimates, time spent, story points.
Skip parents that have children	Counts only the issues at the bottom of the hierarchy, so an epic's estimate and its stories' estimates aren't added twice. Children the tab leaves out (by a filter, say) don't count, so their parent does.
Time in status	How long issues spent in chosen statuses, in working hours or around the clock: total, average per issue, longest or shortest.
Time logged	From worklogs: in any period, by anyone or chosen people. Group by Logged by or Date logged to see who logged what, when.
SLAs (Jira Service Management)	Number breached, number met, least time left, longest and average time taken.
Formula	Any sum of the tab's other values with + − × ÷ and brackets; the formula box lists the values you can use.
Percentage of	A value as a share of the group above, the row's total, the column's total or the grand total.
Running total of	Adds up a value across the columns, starting again for each group of the column groupings before the last.

Values can be shown as numbers, durations (2d 4h), hours, days or percentages, and cells can be coloured by rules.

Tabs

A report can have several tabs over the same issues, each with its own groupings, values, filters and chart. Rename a tab by double-clicking it, or with F2 or Enter. Advanced → This tab only adds a JQL condition for one tab, such as statusCategory != Done; it includes child issues the source added.

Levels and working hours

Levels above epics (Advanced): use issue links to roll epics up into initiatives or themes, for example "is child of". Then group by that level like any other.
Working hours: time in status counts the site's working days and hours (set by a Jira admin), or the report's own. Daylight saving changes are counted at their real length.

Daily history

On a paid plan, turn on Advanced → History → Keep a daily history and save. Once a day the report's totals are taken and kept for 90 days. Then:

Live / History switches the table between now and the latest history. Big reports open from history straight away.
Compare over time charts any value across the days, by group, and Compare two dates shows two days side by side with the change.
More → Update history now takes today's again, at most every 10 minutes.

History is taken once for everyone, then filtered for each person: they see only the projects they can see in full, and names of issues from other projects show as "Restricted issue". Issues with a security level are never kept. In a query, currentUser() means the report's owner. Up to 20 reports per site keep a history; reports nobody has opened in 60 days pause until someone does. A very large report's history may take up to four 15-minute runs a day; if it needs more, the report says how to narrow it.

Share: only me, chosen people and groups, or everyone on the site; and who can edit. Only the owner or a Jira admin can change who a report is shared with. Everyone still sees only the issues Jira lets them see.
Copy link (in Share) links to the report, the open tab and any filters you've changed.
Export the table to Excel or CSV, or the chart as a PNG image. The list behind a cell can be exported too.
Dashboards: the Roll-up report gadget shows one tab of a saved report. It uses the report's latest history when it has one, else it loads live.

For Jira admins

Jira settings → Apps → Roll-up Reports shows every report on the site, with its owner, when it was last viewed, and its history. From there:

Reassign, archive, restore or delete reports, one at a time or in bulk.
Set the site's working days and hours (used for time in status), and its time zone.
Choose who receives reports when their owner leaves the site. If nobody is chosen, those reports show "Owner left" until you reassign them.
Choose who may export: anyone who can see a report, or only people who can edit it.
Turn history off for the whole site.

Plans and limits

Free	Sites with up to 10 users, and sites whose subscription has ended: the full builder, reports of up to 5,000 issues, 3 saved reports, no new history. Moving to the free plan deletes nothing. Atlassian may suspend, and later remove, an app whose subscription has ended; removing it deletes its reports and history, never your Jira issues.
Paid	Reports of up to 50,000 issues, as many saved reports as you like, and daily history for up to 20 reports, kept 90 days.
Trial	The paid plan for 30 days, except that a report's history gets one run a day.
Every report	Up to 4 row groupings, 2 column groupings, 12 values, 10 filters per tab.

Privacy and security

Roll-up Reports runs on Atlassian's Forge platform and calls nothing outside Atlassian. Its data is stored by Atlassian for your site, in your site's data residency location.
It only reads from Jira: it never changes your issues.
Live reports are worked out in your browser and aren't stored.
Accounts Atlassian reports as closed are removed every week.
If we ever retire Roll-up Reports, you'll get at least 90 days' notice to export your reports, and it won't stop before the end of any period you've paid for. When it stops, its reports and history are deleted; your Jira issues stay as they are.

See the privacy policy, the Data Processing Addendum and the terms of use. Questions: support.