Issue tracking

§ ISSUES

Octopush brings your issue tracker into the workspace so you can see what you’re working on without leaving the app. The Jira integration is read-only — Octopush surfaces your tickets, but never edits them. GitHub support is limited to detecting an open pull request for the branch.

Setting up Jira

Open Settings ▸ Integrations and provide:

• Base URL — your Jira site URL.
• Email — the account email.
• API token — a Jira API token.

Then map a project key per Octopush project, so each repository knows which Jira project to read.

[screenshot: Settings ▸ Integrations with the Jira fields]

Note

The Jira integration is read-only. Octopush reads tickets, statuses, and relationships; it does not create, transition, or comment on issues. Ticket statuses are shown exactly as Jira returns them in your account’s language — Octopush never translates them.

What you get

Once connected, a workspace tied to a ticket shows an active-ticket chip with a status dot. From the integration you can see:

• Backlog — the tickets available to pick up.
• Blockers / blocked-by — what’s holding a ticket up and what it’s holding up.
• Subtasks — the ticket’s children.
• Epic navigation — move up to the epic and across its tickets.

Workspaces from tickets

Create a workspace directly from a backlog ticket. Octopush cuts the worktree and auto-links the ticket to it. The link also happens the other way: if a branch name already contains a Jira key, the workspace auto-links the ticket on its own.

GitHub

For GitHub, Octopush detects an open pull request for the current branch via the gh CLI and surfaces it as an open-PR chip in REVIEW.

A typical flow

1. In Settings ▸ Integrations, enter your Jira base URL, email, and API token.
2. Map your project’s Jira key.
3. Open the backlog and pick a ticket.
4. Create a workspace from it — the worktree is cut and the ticket auto-links.
5. Work the ticket; the active-ticket chip keeps its status in view.
6. When you open a PR, the open-PR chip appears in REVIEW (requires gh).

Tips

Caution

GitHub PR detection requires the gh CLI to be installed and authenticated. Jira needs only the base URL, email, and API token — no CLI.

Start from the backlog

Creating a workspace from a backlog ticket auto-links it and (if your branch naming includes the key) keeps the chip accurate for the life of the worktree. It’s the cleanest way to keep code and ticket in sync.