Skip to content

Treetop admin guide ​

This guide is for Jira administrators who install and configure Treetop. For using reports, see the user guide.

Treetop is a read-only Jira Cloud app built on Atlassian Forge. It reads issues, links and worklogs as the person viewing, and it never writes to your issues.

Install ​

  1. In Jira, go to Apps → Explore more apps (or the Atlassian Marketplace) and search for Treetop.
  2. Choose Get app or Try it free and follow the prompts.
  3. Review the access the app asks for and approve it.

Treetop asks for these permissions:

ScopeWhy
read:jira-workRead issues, issue links, worklogs, link types, fields, saved filters and the viewer's own permissions, so reports can be built
read:jira-userShow assignee and worklog author names
storage:appKeep saved reports and Treetop settings in the app's Forge storage

Treetop has no write scopes for Jira data. It declares no external network access and no remote back end.

After installing, everyone who can use Jira can open Apps → Treetop reports. You don't need to configure anything for reports to work. Check the settings below if your site uses unusual story points fields or custom number fields.

Where users find it ​

SurfaceLocation
Treetop reportsApps → Treetop reports
Project pageTreetop in each project's sidebar
Issue panelTreetop button on the issue view
Dashboard gadgetTreetop progress in the dashboard gadget list
SettingsJira settings → Apps → Treetop settings (Jira admins only)

Settings ​

Open Jira settings → Apps → Treetop settings, or choose Configure on Treetop in Manage apps. Only Jira administrators can open or save this page. Anyone else who reaches it sees Only Jira administrators can change Treetop settings.

Settings apply to everyone on the site. Results are still computed with each viewer's own Jira permissions.

Story points fields ​

By default this is empty, and Treetop auto-detects the field. The placeholder shows what it found, for example Auto-detect (Story point estimate (customfield_10016), Story Points (customfield_10028)).

Auto-detection picks, in order:

  1. Fields of Jira's story points type.
  2. Number fields named "Story point estimate" (team-managed projects).
  3. Number fields named "Story Points" (company-managed projects).

Choose fields here only if detection gets it wrong, for example if your site uses a custom number field with a different name. You can choose up to 5. If several are chosen, or detected, each issue uses the first one that has a value, so team-managed and company-managed projects can be mixed in one report.

If no field is found, reports show No story points field found and measure progress by issue count.

Extra number fields to roll up ​

Choose up to 10 number fields to roll up, for example Budget or Business value. Each becomes a column in reports and exports.

They follow the same rule as story points: if any child has a value, the children's sum replaces the parent's own value; otherwise the parent's own value stands. Choosing more than 10 shows Choose at most 10 fields.

By default the issue panel follows only the parent field. Choose link types here to also roll up through issue links in the panel. Each option says which way it works, for example Contains: A "contains" B makes A the parent.

The issue on the outward side of the link is the parent. For a link type such as Contains, "A contains B" makes A the parent of B.

This setting affects only the issue panel. On the report page, each report chooses its own link types.

Maximum levels below the top issue ​

A number from 1 to 12. The default is 8. Hierarchies deeper than this are cut off, and the report shows Hierarchy is deeper than N levels below the top issues; deeper levels are not included.

Raise it if you have deep custom hierarchies or long link chains. Lower it to keep very large reports fast.

Saving ​

Choose Save settings. You'll see Settings saved. Open reports pick them up the next time they run. Fields you didn't touch keep their saved values. Users with a report page already open need to reload it to pick up changed depth or link settings.

Treetop caches the list of detected fields for up to an hour. Saving settings clears that cache, so a new field shows up immediately. If you add a story points field in Jira without saving Treetop settings, it is picked up within the hour.

Permissions model ​

Every query runs as the viewing user ​

Every Jira call Treetop makes uses the permissions of the person looking at the report, panel or gadget. Nobody sees an issue, summary or worklog in Treetop that they can't open in Jira. The same saved report can show different totals to different people.

If a linked issue can't be read by the viewer, Treetop skips it and lists it in a warning, rather than failing the whole report.

People who view a public dashboard without logging in see Log in to Jira to see Treetop reports. Treetop never shows data to anonymous users.

Saved reports ​

A saved report stores only its definition: JQL, link types, pivot, columns, name, visibility, owner, project (if saved from a project page) and timestamps. It never stores issue data or results.

ActionOwnerJira adminOther users
See and run a shared reportYesYesYes
See and run a private reportYesNoNo
Edit or delete a shared reportYesYesNo
Edit or delete a private reportYesNoNo
Save a copy with Save as newYesYesYes, for reports they can see

Jira admins cannot see other people's private reports, and so cannot edit or delete them either. A private report is visible only to the person who created it.

Only shared reports can be shown on a dashboard gadget.

Who can "use Treetop" is anyone with access to Jira on the site. Treetop has no separate user list or role.

Data stored and where ​

Treetop stores three things, all in Forge storage on Atlassian's infrastructure, scoped to your site's installation:

DataContentsKept until
Saved reportsReport definitions as listed above, including the owner's Atlassian account IDThe report is deleted, or the app is uninstalled
SettingsStory points field IDs, extra number field IDs, issue panel link type IDs, maximum depthChanged, or the app is uninstalled
Field cacheThe detected story points, sprint and chosen number field IDs and namesRefreshed every hour

Treetop does not store issues, summaries, story points, time, worklogs or report results. These are read from Jira when someone views a report, computed in that person's browser, and discarded when they leave the page. Exports are created in the browser and downloaded directly; they are never uploaded anywhere.

Nothing leaves Atlassian. Treetop has no remote server and declares no external network access (egress), so it cannot send your data outside Atlassian. Compute and storage run on Atlassian's platform, and data residency follows your Jira site. This is what makes Treetop eligible for the Runs on Atlassian programme.

Treetop does not use AI or language models.

Licensing ​

Treetop is a paid app sold through the Atlassian Marketplace, priced per user and billed with your Atlassian subscription.

  • While the licence is active, or during an evaluation, everything works for everyone.
  • If a paid licence becomes inactive, every surface shows Your Treetop licence is not active. Ask a Jira admin to renew it in Manage apps. Saved reports and settings are kept, and work again once the licence is renewed.
  • There are no feature tiers. Every licence includes every feature.

Manage the subscription in Jira settings → Apps → Manage apps, or in admin.atlassian.com under billing.

Uninstall and data deletion ​

  1. Go to Jira settings → Apps → Manage apps.
  2. Find Treetop, expand it and choose Uninstall.

Uninstalling removes all Treetop surfaces from Jira immediately. Your Jira issues are untouched, because Treetop never changed them.

Saved reports and settings live in the app's Forge storage. Atlassian keeps an app's Forge storage for 28 days after it is uninstalled, then deletes it (Forge storage reference). Solidini holds no copy, because the data never leaves Atlassian.

Before you uninstall, note down the JQL of any reports you want to keep. There is no bulk export of saved report definitions.

To delete individual reports without uninstalling, the owner (or a Jira admin, for shared reports) can delete them from the Saved reports list.

Support ​

Contact info@solidini.com. Include your site URL, the report's JQL and the exact warning or error text.