Every issue tracker you work in, in one list.

One list, every tracker

• Several Jira Cloud sites, Linear workspaces, GitHub accounts (github.com or Enterprise Server) and GitLabs (gitlab.com or self-managed), each issue under its own key: PAY-88, web#412, web!31.
• The pull requests and merge requests waiting for your review, each until your review is given.
• Status, priority, due date and project follow the tracker when they change there. The title and description stay the tracker’s, read only, with your own notes under them.
• New issues wait in the Inbox until you accept or dismiss them.

Run from the keyboard

• A shortcut for every action, each one yours to change in Settings › Shortcuts.
• ⌘K (Ctrl K elsewhere) searches issues by key or title, projects, notes, meetings and actions.
• Select several issues and set their status, priority, plan or project at once.
• A list or a board, grouped and filtered as you like.

Notes in Markdown

Notes, meeting notes and project briefs are Markdown, written rendered: code blocks highlighted by their fence’s language, tables, checklists and pasted screenshots. @ links an issue, a note or a meeting, and @linear retry searches a connected Linear, Jira, GitHub or Notion and links what you pick.

Nothing written unless you say so

opah only reads until you turn on Send status for a connection. Then a status you set goes back, as a Jira transition, a Linear state, or closing and reopening a GitHub or GitLab issue, and nothing else: no comments, no assignees, and pull and merge requests are never written.

How you connect

Each tracker takes a token of your own: a Jira API token, a Linear API key, a GitHub fine-grained or classic token, a GitLab personal access token. opah checks it with the service and keeps it encrypted on its server, where the page never sees it again.