Skip to content

Moving from Pivot Report to Treetop ​

This guide is for teams using Pivot Report (by Colined) on Jira Cloud who want to move to Treetop. It shows how Pivot Report ideas map to Treetop, how to rebuild common layouts, and what Treetop doesn't do yet.

Atlassian ends support for Connect apps on 31 January 2027. Pivot Report's Cloud version is a Connect app. Treetop is built on Forge, Atlassian's current app platform, and runs entirely on Atlassian.

We don't have access to every Pivot Report configuration, so where this guide says "If you used X in Pivot Report…", check it against what your team actually set up.

Before you start ​

  • Both apps can run side by side. Install Treetop while Pivot Report is still installed, rebuild your reports, compare the numbers, then uninstall Pivot Report.
  • Treetop is read-only. It never writes to issue fields, so trying it can't change your data.
  • There is no import. Treetop can't read Pivot Report's saved configurations. You recreate each report, which usually takes a minute or two using templates.
  • Treetop is Cloud only. If you are moving from Pivot Report on Data Center to Jira Cloud, set up Treetop after your issues are migrated.

How the concepts map ​

If you used this in Pivot Report…In Treetop
A report scoped by project, filter or JQLTop-level issues (JQL), or Or start from a saved Jira filter. Give the JQL for the top rows only, such as epics or initiatives. Everything below is found automatically.
A hierarchy built from parent/child (sub-task → story → epic → levels above epic)Built in. Treetop follows the parent field at every level, up to the maximum depth your admin sets (8 by default, up to 12).
A custom hierarchy built from issue linksAlso roll up through links: tick the link types to follow. The issue on the outward side of the link is the parent ("A contains B" makes A the parent).
Grouping or pivoting by a fieldPivot by: Assignee, Status category, Status, Issue type, Project, Sprint, Fix version, Component or Label.
Choosing which values or fields to showColumns. Extra number fields (such as Budget) are added by a Jira admin in Treetop settings, up to 10.
Summed story pointsPoints column and Points done tile. Children's points replace a parent's own estimate when any child is estimated (see below).
Summed time spent and estimatesTime spent (h), Original estimate (h) and Remaining (h) columns, summed at every level.
Progress percentages% done (points) and % done (issues).
Worklog or time reportsThe Time by period tab: logged time per Person or Top-level issue, by Day, Week or Month.
Exporting to a spreadsheetExport CSV and Export Excel. Exports are fully expanded, with a Level column for the hierarchy.
Saved, shared reportsSave report with Everyone who can use Treetop (shared) or Only me (private).
A report on a dashboardThe Treetop progress gadget, which shows one shared saved report.
A roll-up on the issue itselfThe Treetop issue panel.

Check how your numbers were calculated ​

Before you compare totals, check these rules. They are the most common reason two apps show different numbers for the same epic.

Rule in TreetopExample
If any child has story points, the children's sum replaces the parent's own value.Epic estimated 40 with stories of 5 and 8 → 13, not 53.
If no child has points, the parent's own value stands.5-point story with unestimated sub-tasks → 5.
Time spent and estimates are summed at every level, including time logged on the parent.1h on the epic + 4h on its stories → 5h.
Issue counts measure a parent by its children, not by itself.Open epic with all stories done → 100%.
Percentages are rounded down.5 of 13 points → 38%.
An issue reachable through more than one parent is counted once, and the report says so.

If your Pivot Report setup added the parent's own estimate on top of its children's, or counted the parent itself in progress, expect Treetop's totals to differ. Treetop's rules are stated in full in the user guide.

Recreate common layouts ​

Templates are in the Templates panel on the report page. Each one fills in the JQL, pivot and columns and runs the report. On a project page, templates are limited to that project.

Epic progress ​

  1. Open Apps → Treetop reports.
  2. Choose the Open epics progress template.
  3. To include done epics or change the scope, edit Top-level issues (JQL), for example project in (APP, WEB) AND issuetype = Epic, and choose Run report.
  4. Choose Save report, name it and pick who can see it.

Initiative or "above epic" progress using the parent field ​

If your initiatives are parents of epics through Jira's parent field (for example with a custom hierarchy level above epic):

  1. Enter JQL for the top level, for example issuetype = Initiative AND statusCategory != Done ORDER BY rank.
  2. Choose Run report. Epics, stories and sub-tasks below are found automatically.

If you built the hierarchy from issue links in Pivot Report:

  1. If your site has a link type named "Contains…", "Parent…" or "Hierarchy…", choose the Roll up through "…" links template. It selects that link type for you.
  2. Otherwise, enter JQL for the top issues and, in Also roll up through links, tick the link type you used.
  3. Run the report and check a few trees. If an issue is upside down (the child shows as the parent), the link was created in the other direction. Treetop always treats the outward side as the parent.
  4. Links and the parent field are followed together, so the epics you reach by link bring their stories and sub-tasks with them.

Release progress ​

  1. Choose Open epics by fix version. The pivot tab By fix version shows each version's issues, points and time.
  2. Because an issue can have several fix versions, it counts in each, and the page says the groups can add up to more than the total.

Sprint by assignee ​

  1. Choose Active sprint by assignee. It reports every non-sub-task issue in open sprints, with sub-tasks rolled up beneath, and pivots by assignee.

Time spent per epic, and time per period ​

  1. Choose Time spent per epic for estimates against logged time.
  2. Open the Time by period tab. Set From and To, choose Week or Month, and choose Person or Top-level issue for the rows.
  3. Choose Load worklogs. Use Export CSV on this tab for timesheets.

Your own field values ​

If you summed a custom number field in Pivot Report, ask a Jira admin to add it under Extra number fields to roll up in Treetop settings. Then add it in Columns.

Dashboards ​

  1. Save the report as Everyone who can use Treetop. Private reports can't be shown on dashboards.
  2. On the dashboard, replace the Pivot Report gadget with Treetop progress and choose the report.

What's different, or not supported yet ​

Be aware of these before you switch:

Not in Treetop todayNotes
Writing roll-up values back to issue fieldsTreetop is read-only. Values are computed when someone views a report. You can't use Treetop totals in JQL, automation or other apps.
Time in statusNot available. If you used time-in-status reports in Pivot Report, you'll need another app for those.
Gantt charts, scheduling or capacity planningNot available.
Averages, minimums or maximumsTreetop sums and counts. It doesn't average.
Importing Pivot Report configurationsNot available. Recreate reports using templates.
Data Center or ServerTreetop is for Jira Cloud only.
Charts and trend historyTreetop shows tables, tiles and progress bars. It keeps no history, so it shows current values only.
Pivoting on any fieldPivots are limited to Assignee, Status category, Status, Issue type, Project, Sprint, Fix version, Component and Label.
Scheduled or emailed exportsExports are downloaded on demand from the report page.

Other differences to know:

  • Permissions. Every report runs as the person viewing it. Two people can see different totals from the same report if they can browse different projects.
  • Size. The report page reads up to 20,000 issues per report, and the issue panel and gadget up to 5,000. Larger reports show a warning that totals are partial. Narrow the JQL if you hit this.
  • Link direction. Treetop always treats the outward side of a link as the parent. If your links run the other way, the tree will be inverted.

Migration checklist ​

  • [ ] Install Treetop alongside Pivot Report.
  • [ ] Ask a Jira admin to open Treetop settings and check that the detected Story points fields are the ones your teams use.
  • [ ] Ask the admin to add any custom number fields you sum under Extra number fields to roll up (up to 10).
  • [ ] If you use deep hierarchies, ask the admin to check Maximum levels below the top issue.
  • [ ] If your issue panels should follow links, ask the admin to choose link types under Issue panel: also roll up through these link types.
  • [ ] List the Pivot Report reports your teams use, and who owns each.
  • [ ] Recreate each one in Treetop, starting from the closest template.
  • [ ] For link-based hierarchies, tick the same link types and spot-check that parents and children are the right way round.
  • [ ] Compare totals on two or three epics. Explain any differences using the rules above.
  • [ ] Save each report as shared or private, as appropriate.
  • [ ] Replace Pivot Report dashboard gadgets with Treetop progress gadgets.
  • [ ] Tell your teams where Treetop is: Apps → Treetop reports, the project sidebar and the issue panel.
  • [ ] Check whether anyone relied on features in the "not supported yet" list, and plan for them.
  • [ ] Uninstall Pivot Report when you're done. Do it before 31 January 2027 if you don't want to run an unsupported Connect app.

Getting help ​

Contact info@solidini.com. We can help you map a specific Pivot Report layout to Treetop.