The Tickets view
The Tickets view lists the tickets of a Jira project or a GitHub repository next to the selected ticket. In the view you change status and assignee, write comments and import tickets into the projectdocs, for one ticket or for several at once. Everything else is done on the provider's website.
Open it with View › Tickets or Tickets › Show Tickets
(Shift+Cmd+T, Windows/Linux: Shift+Ctrl+T). The activity bar shows the
Tickets icon when at least one ticket provider is configured. The view
needs an open exploration.
Without a provider, the view shows "No ticket provider is configured for this project." and the button Configure Jira…, which opens the Preferences. See Set up ticket providers. Bitbucket issues are not shown in the view.
Filter the list
The filter bar has these controls:
| Control | Effect |
|---|---|
| Provider | Shown when more than one provider is available. |
| Project | The Jira project or GitHub repository. Default is the Jira project key of the exploration. |
| Assignee | Current user or Anyone. |
| Status | One checkbox per status of the project. The statuses come from the provider. By default only Open is ticked. If the project has no status of that name, all statuses of the "To Do" category are ticked. |
| Refresh | Reloads the list. |
The filter is saved per exploration. The status ticks are saved per project. The list is sorted by last update, newest first. Load more fetches the next page.
Search the list
The field Search key, title… above the list narrows the list while you
type. Every word must occur in the key or the title. With Descriptions
ticked, the description is searched too, and the matches are highlighted in the
open ticket. Comments are not searched. Esc clears the search. The menu entry
is Tickets › Search Tickets….
While a search is active, the view loads the remaining pages of the filter result, up to 1000 tickets.
Read a ticket
Click a ticket in the list, or move through the list with the arrow keys. The right side shows:
- the parent ticket, the title, Open in Jira (or Open in GitHub) and Copy link,
- the status, the action buttons and Key details: Assignee, Reporter, Priority, Parent, Labels, Fix versions, Updated,
- the Description, rendered as Markdown,
- the comments, oldest first, and a field for a new comment.
The split between list and detail can be dragged. Its width is saved.
Change a ticket
| Change | How |
|---|---|
| Status | Open the status menu. It lists only the transitions the provider allows for the ticket's current status. A dialog asks for the fields the transition requires and for an optional comment. The comment is added after the transition succeeded. |
| Assignee | Click the assignee. Search for a person, or choose Assign to me or Unassigned. |
| Comment | Write Markdown in Add a comment (Markdown)… and click Comment (Cmd+Enter, Windows/Linux: Ctrl+Enter). Your own comments have Edit. Comments cannot be deleted in Tracemoor. |
After each change the view reloads the ticket from the provider. Errors from the provider appear above the ticket in full.
Hand a ticket to the AI
| Button | Menu | Effect |
|---|---|---|
| Ask AI | Tickets › Ask AI about Ticket | Puts key, title and description into the chat. |
| Fix with AI | Tickets › Fix Ticket with AI | Starts a chat prompt to work on the ticket. The AI reads it with tickets_get. |
| Create Entry | Tickets › Import Tickets to Projectdocs… | Creates a projectdocs entry for the ticket, or refreshes the linked one. See Tickets in projectdocs. |
Tickets › Open Ticket in Browser opens the ticket on the provider.
Act on several tickets
Tick the tickets in the list. The checkbox in the list header selects all visible tickets. A bar with these buttons appears above the list:
| Button | Effect |
|---|---|
| Transition to… | Lists the target statuses that occur in the ticked tickets. For each ticket, the transition to the chosen status is used. Tickets without such a transition are skipped. |
| Assign to… | Assigns all ticked tickets to one person. |
| Add comment | Adds the same comment to all ticked tickets. |
| Import to projectdocs | Asks for a phase and creates one entry per ticket. |
| New work package… | Groups the tickets under a parent and starts a branch for them. See Work packages. |
Before a transition or an assignment runs, a dialog lists every ticket with the old and the new value and marks the skipped ones. You can untick rows there. Fields required by the transition are asked once and used for all tickets. Failures are listed under Some tickets failed; the other tickets are changed.
When you search, ticks on tickets that the search hides are removed, so a bulk action only affects visible tickets.
Changes the AI makes from the chat appear in the view without a manual refresh.