How to use Claude Code with Linear and Jira

Connect Linear with a personal API key, or Jira with an API token (Cloud) or a personal access token (Server and Data Center), on the machine where your sessions run. Then start a session straight from an issue: Claude gets its description, comments and images, works in its own git worktree, and the issue can move to In Progress. When the work is done, Wrap up asks Claude for its summary, and one click moves the issue to In Review.

Connect your tracker

In Commission, open Machines, pick the machine, open its Integrations tab and choose Add integration.

  • Linear: paste a personal API key and pick the team and which issues to show, such as those assigned to you.
  • Jira Cloud: enter your site (your-team.atlassian.net), your Atlassian email and an API token, then the project.
  • Jira Server or Data Center: enter your site's https address, including its path if it has one (jira.your-company.com/jira), and a personal access token from your Jira profile, then the project. This needs Jira 8.14 or later.

Keys stay on that machine and are used only by its sessions, so work and personal accounts never mix. A machine can hold several connections, and you can tie each one to spaces so their issues show there first.

Start from an issue

The Issues page lists your issues from every connection. Open one and choose Start session: Claude gets the title, description, comments and images, and the issue moves to In Progress if that connection's switch is on. You can add a note of your own before the issue.

Commission suggests where to run it from the space the connection is tied to. Choose Change… to pick another folder or machine. Set the permission mode, model and effort the same way as for any new session.

Already working in a session? Use Link issue in its header to attach one, send it to Claude and move it along. The header then shows the issue and its status, and opens it in Linear or Jira.

One worktree per issue

A session started from an issue gets its own git worktree, at .claude/worktrees/<issue> inside the repository, on a commission/<issue> branch taken from the folder's current commit. Two issues in one repository never share a checkout, so their edits and builds don't mix.

It's the Work in its own git worktree switch on New session, on the Mac, in the browser and on the phone. It's on by default for an issue, and you can turn it on for any other session.

Archiving the session removes its worktree and keeps the branch. Its next run adds the worktree back from the branch. Deleting the session removes the worktree, and the branch once it's merged. Commission never forces either: a worktree with uncommitted or untracked changes is left alone.

Review the change

The session's Changes view shows what Claude changed, file by file, with syntax highlighting. Select lines in a diff and add a note for Claude; on the phone, long-press and drag. Your notes collect above the composer, and Send with N notes sends them to Claude in one message.

Finish on the board

You say when the work is done, not Claude. After a finished turn, the session offers Wrap up, which asks Claude to commit what's left and write its summary. It then offers Move to In Review with that summary, which you can edit first. One click moves the issue to its team's review status and posts the summary on it, and every device shows that it's done. With GitHub connected on that machine, the same click pushes the branch and opens the pull request.

Claude is asked to wait for you instead of changing the ticket itself. Nothing changes on your board without your click. Each connection has two switches, In Progress · on start and In Review · your click when done, and turning both off keeps the connection read-only.

File a new issue

Found a follow-up? Choose New issue on the Issues page, pick the connection and the team or project, and write a title and the spec. It's filed with that machine's own key and assigned to you by default. The new issue opens next, so Start session is one click away.

Questions

Does Commission support Jira Server or Data Center?Yes, from Jira 8.14. Connect with your site's address and a personal access token. The machine you connect it on needs to reach the site itself, over https, and trust its certificate. If your company uses its own certificate authority, point NODE_EXTRA_CA_CERTS at it on that machine.
Where are my API keys stored?On the machine you connect them to, used only by that machine's sessions. They never go to a Commission server, because there isn't one.
Can two issues in the same repository run at once?Yes. Each issue session gets its own git worktree and branch, so the two never touch each other's files.
Can I keep my work and personal trackers apart?Yes. Connections belong to a machine, so the issues and keys on your work machine are never used by sessions on your personal one. You can also tie each connection to a space.
Does Claude change my tickets by itself?No. Claude is asked to end with a summary instead of touching the ticket. The issue moves only when a switch you turned on says so, or when you click Move to In Review.
Does it work with Slack too?Slack workspaces open inside the Mac app, beside your sessions.

Start your next ticket from Commission

Connect Linear or Jira on the machine where the code lives, pick an issue, and let Claude start in its own worktree. Commission is free while it's in beta.