Freshness & performance
updated 2026-08-26
Why it’s instant
Traditional rollup gadgets fetch and compute when you open the dashboard — which is why they crawl or time out on large instances. Hierarchy Totals maintains a snapshot of every watched project inside your Jira (Atlassian-hosted storage, nothing external) and renders from it with a single indexed read. Portfolio size barely affects render time: 31,000 issues measure at roughly a second.
When data refreshes
| Trigger | What happens |
|---|---|
| You add a project or field | Sync starts immediately; live preview until it lands |
| Hourly | Incremental sync picks up issues changed since the last pass |
| You view a stale dashboard | Data older than an hour refreshes itself in the background |
| Daily | Full re-sync — the correctness floor that also catches deletions and cross-project moves |
Refreshes are atomic: while a sync is in flight you keep seeing the previous complete snapshot, never a half-written one.
The freshness footer
Every render states its provenance: data as of 2026-08-26 09:34 UTC · 31,237 issues · 1,064 outside hierarchy. If a first sync is still running
you see a live preview, clearly labeled. The app would rather tell you data
is an hour old than pretend it is real-time.
Lifecycle you don’t have to think about
Deleted projects stop syncing automatically. Renamed project keys keep working. Fields removed from Jira are pruned instead of showing confident empty columns. Projects nobody has looked at for 30 days stop consuming sync resources — and pick right back up on the next view.