Dashboard
Planner adds a ticket board and a page for each ticket to the Prompt Studio dashboard. This page explains what you see there and what each control does.
Ticket board
Open Tickets in the project sidebar. The board shows one column for each status, in status order. Newest tickets come first.
To reach off-screen columns, hold the primary mouse button and drag empty board space or a column heading. You can also use the horizontal scrollbar or your trackpad. Dragging a card moves the ticket instead.
Cards
Each card shows the ticket’s title and these properties:
- The ID, such as
PS-12. A sub-ticket also shows the IDs of its parent tickets. - Linked resources: workspaces, artifacts, and resources supplied by enabled extensions. Each badge shows its owner’s current label and icon. Badges wrap within the card. Click one, or focus it and press Enter or Space, to open the resource without opening or dragging the ticket. Unavailable resources retain their saved label with an unavailable indication. Tickets without linked resources show no badges.
- The Type and Priority tags.
- Needs attention, shown by default. Its count opens the ticket’s request forms in the Side Panel while Tickets stays open. Orange counts show pending items; green counts show resolved items. Closing the panel keeps the board open.
Create a ticket
Select the create button at the top of a column. By default only the Backlog column has one. In the New ticket form, write a description in Markdown, attach files if needed, and set the properties, such as tags. The first line of the description becomes the ticket’s title.
The form starts with the column’s status and editable properties that match the current view’s filters. Once the required fields are complete, choose Create ticket or Create without opening in the submit dropdown. The choice changes the primary button and is remembered when the form reopens, including after a reload. Press the primary button to create the ticket with that action. Choosing an option does not create a ticket. Both submit controls stay disabled while the form is incomplete or saving.
Clicking the background keeps the form open. Cancel and Escape close it and keep your draft, including attachments, while this dashboard stays open. Reopen the same view and filter to continue, even after visiting another page. Each view and filter keeps its own draft, so new filtered forms inherit matching properties without replacing earlier drafts. The X discards the current draft. Successful creation clears it.
You can also create tickets from a terminal with pst pstdio.planner create-ticket, or let an agent do it with Planner’s create-ticket skill.
Move and change tickets
- Drag a card to another column to change its status.
- Hold a dragged card near either side of the board to scroll toward hidden columns. Move closer to the edge to scroll faster.
- Choose Manual ordering in the display menu, then drag cards within a column to change their order.
- In the Done column, choose Archive all to archive every ticket in it.
- Select a card to open the ticket page.
Display and filters
The display menu switches between Board and List. It also sets the grouping, the sub-grouping, the ordering, and the properties shown on each card.
Every view, including All, can be edited and renamed. Save your filter and display changes with Save view. Right-click a view to rename, duplicate, or delete it. At least one view must remain.
Use Linked resources in Display settings to show or hide the complete badge list, including workspaces, in Board, List, and Project Timeline. Link, unlink, rename, and owner availability changes refresh the list. The existing workspace display choice now controls this complete list.
Existing saved display choices are preserved. Enable Needs attention in Display settings if a saved view hides it. In Project Timeline, a card with pending decisions or its attention count opens a modal scoped to that ticket. Closing the modal returns focus to its card control.
The board starts with a Ticket is Active filter. Remove it to show both active and archived tickets, or choose Archived to show only archived tickets. Use the filter menu to filter by status, parent, or tag.
To find a ticket quickly, search for it in the command palette. Tickets have their own group there.
Ticket page
The ticket page has three parts: the ticket’s sidebar, the editor, and the Properties panel.
Sidebar
The sidebar lists, from top to bottom:
- The ticket itself. Select it to edit the ticket’s description.
- Needs attention collects ticket actions that need a person. It currently shows review requests and their open count. Select it to answer them while the sidebar stays visible. See Needs attention.
- The Files section lists extra Markdown files that belong to the ticket, and its image attachments. Choose New file to add a file. Right-click a file to rename or delete it. Images open in a read-only preview.
- The Sub-tickets section appears when the ticket has sub-tickets.
- The Workspaces section lists only workspaces explicitly linked to the ticket. The project folder appears only when linked. Tickets without linked workspaces hide this section. Choose Create workspace from the ticket menu to add one. See Attempts.
- The Sessions section lists the agent sessions linked to the ticket, including attempt, review, refine, and sub-ticket sessions.
Editor
The editor shows the document you selected in the sidebar: the description, a ticket file, or an image. Edit the description and ticket files there.
Selecting a saved document puts it in the page URL. Open the menu after the ticket name in the header and choose Copy link to copy that URL. Reload, Back, and Forward restore that document. File links keep working after a rename. A deleted document shows an unavailable error.
Chat links to .pstdio/extension-storage/pstdio.planner/tickets/<ticket>/ticket.md open the exact workspace draft. They do not open or save the Planner document.
Properties
The Properties panel opens beside the editor. It shows the ticket’s ID, its created and updated times, review links, status, dependencies, parent, and tags. It also shows the blocked reason when the ticket is blocked. Change the status and the tags here. You can also copy the ID from the panel.
Ticket actions
The ticket’s actions menu, in the page header, has these actions:
| Action | What it does |
|---|---|
| Run attempt | Starts a managed attempt in a new Git worktree. See Attempts. |
| Refine ticket | Starts an agent session that improves the ticket’s description. You can pick a ticket template and add context. |
| Break into sub-tickets | Starts an agent session that splits the ticket into smaller tickets. |
| Archive | Archives the ticket. Shown on active tickets. |
| Unarchive | Makes an archived ticket active again. Shown on archived tickets. |
| Delete | Deletes the ticket. |
Run attempt, Refine ticket, and Break into sub-tickets let you choose the agent. Refine ticket and Break into sub-tickets open their new session when it starts.
Archiving or deleting a ticket deletes linked workspaces once no active ticket uses them and the project setting Delete linked workspaces (tickets.deleteLinkedWorkspaces) is on. The setting is on by default. Deletion removes the worktree, its branch, and any uncommitted changes. The default project workspace and providers without deletion support stay available. Unarchiving restores the ticket, but does not restore deleted workspaces.
Notifications
Planner sends a notification when a ticket needs you:
- Needs input, when an agent session linked to the ticket waits for your answer. Choose Reply to agent to open the session.
- Review proposal, when an agent marks a proposal ticket as refined. Choose Review proposal to open the ticket. Choose Approve when the proposal is ready, which clears the notification.
Settings
Planner adds these settings for each project:
- Settings → Project Planner → Workflow & automation holds the options for the implement-ticket workflow. See the Planner overview.
- Settings → Project Planner → Ticket tags edits the project’s tags.
- Settings → Project Planner → Ticket status edits the project’s statuses.
- Settings → Project → Templates edits Planner’s ticket, prompt, and document templates. The prompt templates hold the instructions Planner gives agents, for example when it runs an attempt or a review. Edit them to change how agents work on your tickets.
The Ticket tags header keeps Save and Reset visible while you scroll through tag definitions.
Ticket cleanup and merge settings
Archiving or deleting a ticket deletes linked workspaces once no active ticket uses them and the project setting Delete linked workspaces (tickets.deleteLinkedWorkspaces) is on. The setting is on by default. Deletion removes the worktree, its branch, and any uncommitted changes. The default project workspace and providers without deletion support stay available. Unarchiving restores the ticket, but does not restore deleted workspaces.
Archive all updates the board as soon as the tickets are archived. Linked workspace cleanup continues in the background. The host processes up to two workspace deletions at a time across archive batches, API requests, and extension commands. If a deletion fails, cleanup continues with the remaining workspaces and sends a failure notification. The tickets stay archived.
The project setting Mark done on merge (tickets.markDoneOnMerge) is also on by default. Local merges move linked tickets to the status after merge chosen in Planner workflow settings. Without that choice, tickets stay unchanged. Planner checks GitHub pull request links and linked workspace branches every five minutes with up to eight parallel checks. Install and authenticate GitHub CLI (gh) on the host for these checks. Failed GitHub checks leave tickets unchanged and log the failure. Merges do not archive tickets or delete workspaces.
Updated at: 2026-11-05