Arcvale Pivot documentation
Arcvale Pivot for Jira · Product page · Support
Contents
Arcvale Pivot turns any Jira search into a pivot table, chart, issue tree, time-in-status or worklog report. You can save and share reports, export them to Excel, show them on Jira dashboards, and ask the Rovo agent for reports in plain English.
Need help? Email support@arcvale.app.
1. Getting started
- A Jira site admin installs Arcvale Pivot from the Atlassian Marketplace.
- In Jira, open Apps → Arcvale Pivot.
- Click New report, type a search (JQL) and press Run.
No setup is needed. Arcvale Pivot finds your story points, sprint and custom fields automatically.
2. Build a report
- Search (JQL). Any Jira search works. For example
project = APP AND sprint in openSprints(). To use a saved filter, typefilter = 12345. - Rows. What each row is grouped by.
- Columns (optional). A second grouping across the top.
- Value. What to count or add up.
- Show. Sum, Average or % done.
- Press Run.
What you can group by
- Project, status, status category, issue type, priority, resolution
- Assignee, reporter
- Epic / parent, epic roll-up (an epic including the sub-tasks of its stories), initiative
- Sprint, labels, components, fix versions
- Dates (created, updated, resolved, due date, or any date field) by week, month, quarter or year. Empty periods are shown as zero, so trends are honest.
- Custom fields: select, multi-select, cascading select, user picker, number, date, text
- Check: the warning type (see section 5)
Swap rows and columns with the ⇄ button.
Drill down. Click any number or bar to open the exact issues behind it in Jira's issue search.
Multi-value fields. An issue with two labels appears in both label rows. The total counts each issue once.
3. Values and calculations
| Value | What it means |
|---|---|
| Issue count | Number of issues |
| Story points | Sum of story points |
| Time spent | Hours logged |
| Original estimate | Estimated hours |
| Remaining estimate | Hours left |
| Lead time | Days from created to resolved (resolved issues only) |
| Age | Days an open issue has been open |
| Days since update | Days since an open issue last changed |
| Days overdue | Days past the due date (open issues only) |
| Any number field | Your own number custom fields |
Show
- Sum: the total.
- Average: the average per issue. Best for lead time, age and days since update.
- % done: the share of the value in Done issues, e.g. % of story points completed per epic.
Issues where a value doesn't apply (like lead time for an open issue) are left out of sums and averages, not counted as zero.
4. Report types
Use the tabs at the top of the report.
Pivot. The cross-tab described above. View it as:
- Table, with an optional heatmap that colours bigger numbers darker
- Bars, stacked by the column grouping
- Trend, a line chart. Put a date (by week or month) on the rows.
Issue tree. Initiative → epic → story → sub-task. Each level shows rolled-up totals of everything below it and a progress bar. Grey rows are parents that are outside your search but are shown to complete the tree. Use Expand all and Collapse all.
Time in status. How long issues spend in each status, from each issue's history. Shows total or average days per issue, grouped by any field. Use it to find where work gets stuck (for example "In Review").
Worklogs. Pick a start and end date. See hours logged per person by day, week or month.
- Hours count for the person who logged them, not the assignee.
- Only Jira's own work log is read. Time kept only in another tool won't appear.
5. Needs attention warnings
Above every report, a yellow strip counts the issues in your search that need attention:
- Overdue: past the due date and not done
- Flagged as blocked: flagged as an impediment
- Unassigned: open with no assignee
- No update in 14+ days: open and not touched for two weeks
- No estimate: open with no story points or time estimate
- Done but time remaining: done, but remaining estimate is still above zero
Click a warning to open those issues in Jira. To see warnings by person or epic, set Rows to Check.
6. Save and share
- Click Save and name the report. You are its owner.
- Save as makes a copy you own.
- The Reports page lists every report you can open, with search.
- Share a report with:
- Only me
- Everyone on the site who uses the app
- Specific people and groups, who can view or edit
- Copy link gives a link to the report.
- Sharing controls who can open a report. Everyone still sees only the issues their own Jira permissions allow, so numbers can differ between people.
- Jira admins can see and manage all saved reports.
7. Export
Click Export:
- Excel (.xlsx): a formatted spreadsheet
- CSV: for Google Sheets and other tools
8. Dashboard gadget
- Open a Jira dashboard and click Edit, then Add gadget.
- Search for Arcvale Pivot report and add it.
- Choose a saved report and save.
The gadget shows the report live. Each viewer sees the numbers their own permissions allow. If the report is not shared with a viewer, the gadget says so instead of showing data.
9. Rovo agent and Ask Rovo
These need Rovo to be turned on for your site.
Arcvale Pivot Analyst agent. Open Rovo chat, choose Arcvale Pivot Analyst, and ask a question. The agent turns it into a search and a pivot, runs it as you, and answers with a short summary, a table and a link to open the full report.
Example questions:
- "Who has the most open work right now?"
- "How far along is each epic? Show % done by story points."
- "What needs attention in project APP?"
- "Hours logged per person this month."
- "Bugs created by week this quarter, split by priority."
- "Average lead time by issue type."
- "Open issues by Team" (uses your custom field name)
Ask Rovo button. In any report, click ✦ Ask Rovo. Rovo opens with a question about the report on screen and explains what stands out and what to do next.
The agent's answers are AI-generated. Check important numbers in the report itself.
10. Limits
- Up to 5,000 issues per report in the app.
- Up to 2,000 issues per agent question.
- When a result is capped, the app tells you. Narrow the search (by project, date or sprint) for complete numbers.
11. Permissions and privacy
- Arcvale Pivot reads Jira as you. It never shows issues you can't already see.
- It never changes Jira data.
- It stores only saved report settings (name, search, layout, owner and sharing list) in Atlassian's Forge storage. It does not store issue content.
- It runs entirely on Atlassian's platform (Runs on Atlassian). No data is sent to Arcvale Apps or anyone else.
- Permissions:
read:jira-work,read:jira-user,storage:app.
Privacy policy: https://arcvale.app/pivot/privacy · Terms: https://arcvale.app/pivot/terms
12. FAQ
Why is a number different for my colleague?
Each person sees only the issues they have permission to see.
Why don't I see story points?
Arcvale Pivot looks for a field called "Story points" or "Story point estimate". If your site uses another name, choose it under Value as a number field.
My search is slow or capped at 5,000.
Add a project, sprint or date range to the JQL.
I don't see the Rovo agent.
Rovo must be enabled on your site, and you may need to search for "Arcvale Pivot Analyst" in Rovo's agent list.
Moving from Pivot Report?
Arcvale Pivot uses the same rows / columns / value layout. Email support@arcvale.app and we'll help you rebuild your reports.