Cache & refresh
Foundation keeps a local copy of every Jira issue that appears in your lenses. This “issue cache” is how the app shows columns, progress, and rollups without pounding the Jira API every time you open a lens. Most of the time you never think about it — the cache updates automatically.
Read this page when data looks stale or when a site admin needs to reset things after an import or migration.
How the cache stays fresh
Section titled “How the cache stays fresh”- Foundation subscribes to Jira’s
avi:jira:updated:issueandavi:jira:created:issueevents. These are free events — they don’t cost rate-limit points. - When Jira fires an event, Foundation fetches the full issue and upserts it into the cache.
- Sync Agents explicitly hit the Jira API on demand to pull fresh data into lenses.
- When you open a lens, Foundation reads the cache, enriches the tree, and serves you the result.
Typical end-to-end lag: seconds for event-driven updates, minutes for larger background jobs.
Refresh a single lens
Section titled “Refresh a single lens”If a column looks stale in one lens, refresh that lens only:
- Open the lens.
- In the toolbar, click the Refresh button (circular arrow icon), or open the command palette with
/and choose Refresh data. - Foundation re-reads the cache and re-applies filters, sort, and formatting.
For individual issues, open Issue details in the Inspector and click Refresh from Jira to pull that one issue straight from the REST API.
Force a site-wide cache refresh (admin)
Section titled “Force a site-wide cache refresh (admin)”If the whole tenant looks out of date — typically after a Jira import, a migration, or an event-handler outage — a site admin can refresh or purge the cache:
- Go to Apps > Manage your apps > Foundation > Configure.
- In the Cache section:
- Click Refresh all caches to re-pull every tracked issue from Jira. This spends API points proportional to the number of cached issues.
- Click Purge cache to clear the cache entirely. Lenses reload their data the next time they’re opened.
Prefer refresh over purge when possible — a refresh keeps lenses usable during the rebuild; a purge leaves them empty until users reopen them.
Known cache gotchas
Section titled “Known cache gotchas”- Custom workflow notifications (ECO-395) — some Jira workflows use custom event notifications that do not fire
avi:jira:updated:issue. Issues moved through those transitions may sit stale in the cache for up to an hour. A manual refresh works around it. - Permission changes — BROWSE checks are cached per user for 15 minutes. Cache refresh does not reset that; the user’s own check simply expires.