Jira

Connect a Jira site with an API token and work issues from the sidebar.

The Jira integration surfaces issues from your Jira site inside Tegment, so you can create a worktree from an issue, assign it, and move it through its workflow without leaving the app.

Connect#

Open Settings → Jira and add a connection. Tegment authenticates with an Atlassian API token — not a browser OAuth flow. You provide four things:

• Connection name — a label, so you can connect more than one site.
• Site URL — e.g. https://your-domain.atlassian.net.
• Email — the account the token belongs to.
• API token — create one from Atlassian's API tokens page; Tegment links you there.

The token is stored encrypted on your machine.

Pick a project#

Each Tegment project is linked to one Jira connection and one Jira project, identified by its project key — PROJ, WEB, and so on. Issue keys like PROJ-456 belong to project PROJ. You set this per project in settings, alongside the branch-name pattern used when you create a worktree from an issue.

What you get#

• Issues in the sidebar, grouped by saved JQL sections you define per project.
• Browse and read — open the issues from your filters and read their full descriptions without leaving Tegment.
• Start work from an issue — create a worktree for it (the branch is named from the issue key and summary) and hand it straight to an agent with a quick action. The agent pulls the issue's details over the MCP server, so it starts with the full context.
• Assign and transition issues — pick up an issue and move it through its workflow from Tegment.

Move an issue when you start work#

Tegment can transition an issue for you the moment you create a worktree from it, so the board reflects what you're actually doing without a second trip to Jira.

Set it up under Settings → Jira for the repository you're working in:

• Auto-transition issue when creating worktree turns it on.
• From status limits it to issues sitting in the statuses you pick. Leave it empty to apply to any status.
• To status is where the issue lands. The list comes from your Jira project's own workflow.

Each repository gets its own settings, so a team using To Do → In Progress and one using Backlog → Selected for Development can both have what they want.

That configuration is the whole opt-in: there is nothing to tick as you start work. Every issue you start is checked against From status on its own and moved to To status if it matches, whether you started one issue or ticked several at once. An issue sitting outside the source statuses is left where it is, and a transition that fails doesn't hold up the worktree or the agent.