The local copy
The projects you choose are cached in a local database, so search is instant and the board still reads when Jira is unreachable.
PrivateGoat keeps its own copy of the Jira issues in the boards you chose, in a SQLite database on the Mac. Opening a board, filtering it or searching it does not wait for Jira, and the copy is readable offline or after you sign out.
How to use it
You do not have to do anything to keep the copy: it updates in the background while the Jira surface is open.
| Situation | What happens |
|---|---|
| Jira surface open | An incremental catch-up about once a minute |
| Jira surface open | A full check about every 15 minutes |
| A sync failed | A five-minute back-off, then a retry |
| Any time | The sync button in the Jira header forces a check |
| No connection | The last copy is shown, with a notice |
What is in the copy
| Kept | Not kept |
|---|---|
| Rank, status, assignee, created date | Comments |
| Description | Attachments |
| Parent and child links | Anything that would make the copy a second Jira |
| Sprint membership |
Sign Out of Jira… in the Jira surface asks which you want: Sign Out and Keep the Copy keeps the cache readable and stops syncing; Sign Out and Delete the Copy removes it from this Mac.
Settings
| Setting | Where | Notes |
|---|---|---|
| Connection and editing | Settings → Jira | See Connect Jira |
| Boards | The board picker in the Jira surface | Per account |
There is no sync-interval setting; the schedule above is fixed.
What is stored
| Item | Where |
|---|---|
| Accounts, scopes, issues, scope membership, sprint/rank, the operation ledger | ~/Library/Application Support/Sonavia/jira.sqlite3 |
| The sign-in itself | The macOS Keychain (see Keys and sign-ins) |
What leaves your Mac
The sync's reads go to https://mcp.atlassian.com/v2/mcp, Atlassian's hosted MCP gateway, using the
account you signed in with. The cached board itself is local. Nothing else receives Jira data, and the
local MCP server never calls Jira — agents see the last copy even when Jira is unreachable.
When it is off or fails
- Signed out:
Signed out of <site>. The list below is the copy PrivateGoat already has.The copy stays readable and stops updating. - A failed sync: a notice appears in the Jira surface, the last copy stays on screen, and the retry backs off for five minutes.
- An expired token: it is renewed; if that fails, the app asks for sign-in and keeps your draft.
- No Jira account at all: there is no copy and no Jira surface; PrivateGoat is a meeting recorder until you connect Jira (see Connect Jira). Signed out with the copy kept still counts as having Jira.
- Comments and attachments: they are never in the copy, so they are not searchable offline.
Related
- Connect Jira — the sign-in and the projects.
- Tree and board — the two views over the copy.
- Quick Find — search that reads the copy instantly.