Connect Jira
Jira is optional. Connect it any time: sign in with Atlassian in your browser, then choose the projects PrivateGoat keeps a copy of.
Jira is optional. PrivateGoat works as a meeting recorder on its own; connecting Jira adds your board, Quick Find over your tickets, and sending a meeting's to-dos as issues. Connecting is a browser sign-in with Atlassian and a choice of projects. There is no token to paste, no app password and no broker in between: the app talks to Atlassian's hosted MCP gateway, and the grant is kept in the macOS Keychain.
Without Jira
Until an account is connected, nothing Jira-shaped appears:
- no Jira place in the sidebar, and no ticket tree in the Timeline;
- no Send to Jira on meetings or to-dos (⌘J does nothing);
- no Jira scope in Quick Find (⌘4 does nothing; the other numbers keep their meaning);
- no ⌃⌥J lookup, no Daily Scrum or Stand-up items in the Window menu, no sprint card on Home;
- no terms learned from Jira in Words and Terms;
- no Jira tools in the local MCP server: agents get 18 of its 22 tools.
An account in any state — connected, expired, or signed out with the copy kept — counts as having Jira, so those surfaces stay and ask you to sign in again. If the Jira cache cannot be read, Jira stays hidden.
How to use it
- Choose Connect Jira… in Settings → Jira, or on the welcome tour's step Does your team plan in Jira? (offered only while no Jira is connected; Not Now is the default and changes nothing). The sign-in sheet offers Connect with Atlassian. Once connected, Settings → Jira → Connection shows the status and opens the Jira surface, where you sign in, sign out or remove the account.
- Approve the request in your browser — Atlassian's own sign-in page — and come back to the app.
- The app then asks Atlassian's MCP gateway, over the grant, which sites the account can reach and who the
account is; on a site whose browse address it cannot yet prove, it checks each candidate host against
Atlassian's
tenant_info. - Pick your projects. In the Jira surface, Add Board… lists your recent projects; choose the ones you want cached. Remove Board takes one out again.
The Status row in Settings → Jira reads Not connected, Connected, Sign-in needed — … or Connection failed — …; it does not name the site. From then on, the boards, the tree, the Daily Scrum, Quick Find and the local MCP server all answer from the local copy — see The local copy.
Settings
| Setting | Where | Notes |
|---|---|---|
| Connect Jira… | Settings → Jira, or the welcome tour | Shown while no Jira is connected |
| Connection status, Open Jira in PrivateGoat | Settings → Jira → Connection | Per account, once connected |
| Enable editing in Jira | Settings → Jira → Editing | Creating and changing issues; see Create and edit tickets |
| Boards | The board picker in the Jira surface | Add Board… and Remove Board, per account |
What is stored
| Item | Where |
|---|---|
| The Atlassian sign-in (the OAuth/MCP grant) | The macOS Keychain — see Keys and sign-ins |
| Accounts, scopes, issues, scope membership, sprint/rank, the operation ledger | ~/Library/Application Support/Sonavia/jira.sqlite3 |
| Board choices | Per account, in the app's preferences |
The grant is not written to a file the app can read back as text.
What leaves your Mac
- Browser sign-in: Atlassian's own sign-in page, which sees the account sign-in as any browser sign-in does.
- The account and its sites:
https://mcp.atlassian.com/v2/mcp, Atlassian's hosted MCP gateway, answersatlassianUserInfoandgetAccessibleAtlassianResources. - The site address check: when the gateway names no browse address, up to three candidate hosts drawn
from links, plus one guessed from the sign-in email address when it is not already among them, are asked
for
https://<host>/_edge/tenant_infountil one answers with the granted cloud id. - Reads and writes: the same gateway,
https://mcp.atlassian.com/v2/mcp. - The redirect back: a loopback listener on
127.0.0.1on an ephemeral port.
Nothing else receives Jira data. There is no PrivateGoat server and no broker of ours.
When it is off or fails
- No account: PrivateGoat is a meeting recorder, and every Jira surface listed under Without Jira is hidden. Removing the account together with its copy returns to this state.
- A read-only grant: the edit controls are hidden and the app explains that reconnecting in Settings → Jira can request editing.
- A failed sync: the last copy stays on screen with a notice, and the app retries with a back-off.
- Signed out: Sign Out and Keep the Copy leaves the cached issues readable but frozen; Sign Out and Delete the Copy removes them from this Mac.
- An expired token: it is renewed; if a real sign-in is needed, the app asks and keeps your draft.
Related
- The local copy — what is cached and how often it updates.
- Keys and sign-ins — where the grant lives.
- What leaves your Mac — the complete network list.