Omniscio

Jira board

A first-party integration that brings your Jira Cloud board into Omniscio so you can work issues without opening the Jira website: pick a board, see its columns and cards, open an issue's description and comments, and move work. It is gated through the unreleased-feature registry, so it stays hidden until enabled.

On this page

What it is

Status: in development. Turn it on in Settings → Lab → "Jira board" (or set AMC_SHOW_JIRA_BOARD=1); the "Jira" sidebar row appears once it is on.

A first-party Omniscio integration that brings your Jira Cloud board into the app so you can work issues without opening the Jira website. It surfaces as a "Jira" row in the projects sidebar (between Inbox Pilot and Job Monitor) that opens a full-pane board view.

It is gated exactly like the Pull Requests tab — through the unreleased-feature registry (jira-board), not a plain feature flag — so it stays invisible until a developer flips its status to shipped.

Where to find it

Once enabled, a Jira row appears in the projects sidebar (between Inbox Pilot and Job Monitor); clicking it opens the full-pane board view. The enable switch is Settings → Lab → Jira board.

How it behaves

How to use it

  1. Enable it: Settings → Lab → toggle Jira board on. A "Jira" row appears in the sidebar.
  2. Connect (in the panel): open the Jira sidebar row and click Set up Jira (or the header gear, which carries a status dot). In the drawer, enter:
    • Site URL — your Jira Cloud address, e.g. https://your-site.atlassian.net
    • Atlassian email — the account you log into Jira with
    • API token — create one at id.atlassian.com → Security → API tokens
  3. Click Save. A green dot + "Connected as …" confirms it works. The gear stays in the header to update credentials later.
  4. Open the Jira sidebar row:
    • Pick a board from the dropdown (top-left).
    • See your columns (To Do / In Progress / Done…) with issue cards (key, summary, type, assignee).
    • Click a card to open the issue detail drawer on the right — description and comments (rendered from Jira's rich text), status, assignee, reporter, priority, labels, and a link to open the issue in Jira.
    • Refresh re-pulls the current board.

Working issues (no browser needed):

  • Create a new issue with + New issue (top-right) — pick a type, write a summary/description, optionally set priority + labels.
  • From the detail drawer you can Move the issue (the Move to… dropdown only offers the transitions Jira allows), Assign it (Assign to me, search a teammate, or Unassign), Comment (Ctrl+Enter to send), and edit the summary, description, priority, and labels in place (hover for the pencil).

Getting around a big board:

  • Drag a card to another column to move it (only where Jira allows the move).
  • Filter box (top-right) narrows the visible cards by text — key, summary, assignee, or label.
  • On a Scrum board, a scope dropdown switches between the board, Backlog, and each sprint.
  • Load more at the bottom pulls in the next batch when a board has lots of issues.

Stop checking the board — let it come to you: turn on Settings → Lab → "Jira issues assigned to me in Inbox". Omniscio then checks Jira in the background (every few minutes, only while on) and surfaces your assigned, not-done issues as rows in the unified Inbox — and when one of them updates, its row pops back to the top so you notice. Click a row to jump to it on the board; snooze or dismiss like any inbox item. Requires the Jira board (above) enabled and connected. Kill switch for power users: AMC_DISABLE_JIRA_INBOX_POLL=1.

Your API token is encrypted at rest on your device and is never shown back to you or sent to the renderer once saved.

Troubleshooting

Each message below is the exact copy the app shows.

  • "Connect Jira in Settings → Optional Features → Jira connection first." — no credentials are saved. Open the Jira sidebar row and use Set up Jira; the Settings row at Settings → API Integrations → Jira opens that same panel (the message's "Optional Features" is that section's older name).
  • "Invalid email or API token — double-check both and try again." — Jira refused the pair (a 401 or 403). The email must be the Atlassian account that owns the token, and the token may have expired or been revoked at id.atlassian.com → Security → API tokens.
  • "Couldn't find that Jira site — check the URL." — a 404 from the site URL. Use the full https://your-site.atlassian.net address, with no path after it.
  • "Jira rejected the request (HTTP 400) — check the connection's settings and try again." — Jira received the request but would not accept it. In practice this is a JQL or field problem (an unknown status, field or function in the query, or a transition the issue does not allow). Correct the query or open the issue in Jira.
  • "Jira is rate-limiting requests — wait a moment and try again." — Jira's request limit was reached; the queue already retried once.
  • "Couldn't reach Jira — check the site URL and your connection." — the request never got an answer: offline, a proxy, or a Jira outage.
  • pull-requests.md — the closest analog; same gating + service → IPC → store → UI shape.
  • Contract: .claude/memory/contracts/jira-board-contract.md — the invariants and the tests that lock them.

Last verified 2026-10-25