RollGrid for Jira
Pivot tables, roll-ups through the work-item hierarchy, and worklog timesheets over any filter, JQL, space or work item. Runs entirely on Atlassian.
RollGrid answers the reporting questions Jira dashboards cannot: how many story points sit under this initiative, where last week's logged time actually went, which teams are over capacity, and what is quietly overdue.
- Your first reportFive minutes, start to finish.
- Start from a templateFive ready-made reports.
- Moving from Pivot ReportConnect support ends January 31, 2027.
What it does
You pick a source, RollGrid reads it once, and every tab on the report works off that one read.
| Tab | What it shows |
|---|---|
| Structure | A tree from sub-task to story to epic to initiative, with numbers rolled up each level and a progress bar |
| Pivot | Any field down the side, any field across the top, counts or sums or averages in the cells |
| Timesheet | Logged time by person, team or field, in days, weeks, months or quarters |
| Capacity | Remaining estimates against working hours, after weekends, holidays and leave |
| Warnings | Overdue, over estimate, unassigned, stalled, or done with children still open |
Charts arrive in the next update. Everything above is in the current release. A charts tab can be saved on a report today, and it will say so on screen until the update lands — it is not offered when you add a tab, so you will only see this if someone saved one.
Where it lives in Jira
- Apps → RollGrid — all your reports, and the templates.
- A space's sidebar — the reports for that space.
- A dashboard — two gadgets, so a report sits beside everything else. See gadgets and widgets.
- Jira settings → Apps → RollGrid — admin settings, for Jira admins.
It only ever shows you what you can already see
Every read of Jira is made in your browser, as you. A report shared with ten people shows each of them the work items they have permission to see, which means two people can open the same report and get different totals — correctly. Cached results are kept per person and are never shown to anyone else.
Nothing leaves Atlassian. There is no server of ours in the path, no analytics, and no outbound connection of any kind. See security.
The limits, up front
- A report reads up to 20,000 work items. Above that it asks you to narrow the source, or an admin raises the limit. Hitting the limit is always said on screen, because a missing child makes a roll-up read low.
- Results are cached per person for 30 minutes by default. The report says how old they are, and Refresh asks Jira again.
- Uninstalling deletes everything RollGrid stored. See before you uninstall.