project = KEY.Type a JQL query or pick one of your saved filters. ORDER BY is ignored. Ctrl/Cmd+Enter runs the report. Reports read up to 5,000 issues, page by page with a progress bar; if a query matches more, a notice says so and the numbers cover the first 5,000.
| Type | What you get |
|---|---|
| Pivot table | Rows (one field, optionally a second for subtotals) × columns (any field, or none). Values: count of issues, or sum / average / minimum / maximum of a number field such as story points, original or remaining estimate, time spent or any custom number field. Sort rows by name or by value. |
| Hierarchy roll-up | The query picks the top issues, for example issuetype = Epic AND project = OPS. Their children and sub-tasks (up to three levels) are fetched automatically, and the chosen numbers are summed up the tree. A % done bar shows the share of issues in a Done status category. |
| Worklogs | Hours logged by author (or by project, epic or issue) per day, week or month in a date range: last 4 or 12 weeks, this or last month, last 3 or 6 months, this year, or custom dates. The JQL is optional (empty = every project you can see). |
Project, issue type, status, status category, priority, assignee, reporter, labels, components, fix versions, affects versions, resolution, parent (epic), sprint, created / updated / resolved / due date by week, month, quarter or year, and custom fields of these types: single select, radio buttons, multi select, checkboxes, user picker, labels, date and date-time. Multi-value fields (labels, components, sprints…) count an issue in every value it has; totals still count each issue once.
Name a report and press Save (or Save as new). Saved reports are shared with everyone on the site who can open PivotPulse; anyone can open, change or delete them. Each person still only sees issues they have permission to browse. A dashboard gadget keeps its own copy of the report, so editing a saved report later does not change gadgets.
worklogAuthor and worklogDate, which Jira matches per issue, not per worklog.Pivot Report is a Connect app; Connect apps can no longer receive new features and Atlassian ends Connect support. PivotPulse covers its main reports on Forge: pivot by any standard or select field, Epic → story → sub-task roll-up with estimates and % done, and time logged per person per week or month (the Worklogs Report use case). There is nothing to migrate: install PivotPulse, recreate your favourite reports with the same JQL or saved filters, and save them. Both apps can stay installed while you switch.
PivotPulse runs on Atlassian and makes no external calls. On the Reports pages and the gadget, issues and worklogs are read in your browser with your permissions. When you use the Rovo agent, they are read in the app's Forge function on Atlassian, also with your permissions, and the resulting table is returned to Rovo. In both cases they are never stored. The app keeps only saved report definitions in Forge storage, without account IDs or names. The rating prompt remembers its state in your own browser only (localStorage), never on a server. See the privacy policy.
Email support@puzaricloud.in.