Issues

Browse, create, plan, and start work on GitHub and Jira issues from one place.

Once you've connected GitHub or Jira, Tegment opens their issues in a single issue browser: one modal that browses, creates, and starts work on issues, and shows how they depend on each other. It works the same way for both integrations, showing whichever source you opened.

Open it with Ctrl+Shift+G for GitHub or Ctrl+Shift+J for Jira, or from the integration's section in the sidebar. The browser lists issues on the left and shows the selected issue on the right. The search box has focus when it opens, so you can start typing straight away.

Browsing#

Issues are grouped into sections, the saved filters you define per repository (see Issue sections for how to set them up). Each section shows a handful of issues with a total count; use Show more to reveal ones already loaded, then Load more to fetch the next page. The search box at the top finds an issue by number, key, or keywords without a saved section.

Narrow the list with filters that adapt to what's loaded: repository, labels, assignee, milestone (GitHub), and priority, epic, or type (Jira). The To do toggle narrows the list to the tickets on your project's To do list. Filters combine, and each shows as a removable chip. They are kept while Tegment runs, per project and per source, so reopening the browser brings them back.

Creating an issue#

Select New issue in the browser header and fill in the form on the right. The fields follow the integration:

• GitHub: title (required), description, labels, and milestone.
• Jira: issue type (required), summary (required), description, priority, epic, components, and labels.

Descriptions take Markdown. Tegment creates the issue live in GitHub or Jira and adds it to the list. If the connected account can't create issues in that repository or project, the button is disabled and tells you why.

Blocked by and Blocks#

A ticket's details list the tickets that block it and the ones it blocks, under Blocked by and Blocks, each with its status at the source. Click one to open it in the browser. When something a ticket depends on isn't done yet, the details say so above the lists, with a link to the dependencies view. In the list, a ticket carries Blocked by and Blocks badges while those tickets are still open.

The links come from GitHub and Jira themselves, so you link tickets with "blocks" there and Tegment shows them.

The dependencies view#

Switch the browser header from List to Dependencies to see the tickets as a graph of what waits on what. The graph covers every ticket your search and filters leave, and the details pane stays beside it.

• Each card is marked Blocked or Ready. Select one to highlight the chain of tickets it waits on.
• The legend tells apart a link that blocks now, one that is satisfied because the blocker is done, and the waiting chain of the selected ticket.
• Tickets without any links are hidden; Show brings them in.
• For Jira, Move… beside the count of ready tickets moves all of them to a status at once.

Drag to move around the graph, and zoom with the buttons in the toolbar or Fit to view.

Changing status#

For a Jira ticket, click the status in its row to move it to any status its workflow allows from there. With several tickets selected, Change status in the action bar moves them all, offering only the statuses every one of them can move to. If some can't be moved, Tegment says how many.

GitHub issues have no workflow to move through, so their status stays as it is.

Starting work from an issue#

Select an issue to set up its work in the detail pane: an editable branch name, the base branch, the agent, a quick action to launch, and, for an agent that offers it, the model and effort this run should use. Choose Start work (or press Ctrl+Enter) and Tegment creates the worktree, routes it into a terminal group if one is bound to it, and starts the agent. If a worktree for the branch already exists, you get Open Worktree and Run in existing worktree instead.

To set the work up in New session instead, choose Link: the ticket goes into the project's New session draft, where you can add to the prompt and pick where the agent works.

The agent picker lists only the agents Tegment can actually find on your machine, so a launch is never offered that couldn't run. With none installed, the pane says so and the start is blocked rather than failing later. See Supported agents for the model and effort control.

The setup runs in the background. Its terminal appears immediately and names the step it is on, the browser releases as soon as the work is accepted, and you can carry on elsewhere in the app while it finishes. The agent boots as soon as the worktree exists, so a slow npm install doesn't stand between you and a usable agent: your setup scripts run alongside it, with their own row on the status bar. Start several issues in a row and their worktrees are created one after another rather than competing over the same repository.

If something fails, the error lands in that terminal's pane and in a notification, with nothing left half-created. A failing setup script shows on the status bar until you dismiss it, without taking the screen from the agent you're already working in.

Working on several issues at once#

Check the box on any issue row to select it, and Shift-click to select a range. With issues selected, the action bar lets you:

• Start work on all of them. You pick the agent, quick action, and base branch once, and Tegment creates a worktree and starts the agent for each in turn. Batches of five or more warn you first, since each one spawns a worktree and terminal. Jira auto-transition applies to each ticket in the batch, judged on that ticket's own status.
• Change status to move Jira tickets to the same status.
• Add to To do to put them on the project's To do list.
• Assign to me to take ownership of each.

Settings#

• Keep issue modal open after starting task (Settings → General, off by default): keeps the browser open after you start work, so you can queue up several issues in a row.
• Move the issue when you create a worktree (the repository's Jira issues settings page): moves a Jira issue to a status you choose when you create a worktree from it. See Jira.