Issues
Browse, create, edit, 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, edits, and starts work on issues. 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.
Browsing#
Issues are grouped into sections, the saved filters you define per repository (see Issue sidebar & saved filters for how to write them). 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). You can also filter to issues that are On a to-do list. Filters combine, and each shows as a removable chip.
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.
Editing an issue#
For a GitHub issue, edit its labels and milestone inline in the detail pane and choose Save changes; Tegment writes the change straight back to GitHub. For a Jira issue, you assign it to yourself and move it through its workflow (see below) rather than editing fields inline.
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, and a quick action to launch. Choose Create Worktree (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.
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.
- Add to to-do to drop them onto a 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.
- Auto-transition (Settings → Jira, per repository): moves a Jira issue to a status you choose when you create a worktree from it. See Jira.