See the complete route index at https://docs.crusible.dev/llms.txt before following links. # Issues Issue lists, saved board views, editable attributes, dependencies and activity, with the boundaries between filing an issue and asking the agent to work on it. Issues keeps a work item's description, assignment and activity together. Selecting an issue opens its detail pane. On a narrow screen, the pane covers the list; closing it returns to the list. Issues are records in Crusible. A Linear-backed issue surface and two-way Linear synchronisation are unavailable. ## Lists and board views A plain channel's list and a board's saved view offer different filters and sort options. The open view determines which controls appear. | Control | Plain channel | Board view | | --- | --- | --- | | Search | Search the channel's issues | Search within the resolved board view | | Filters | Status, priority and assignee | Status, priority, milestone and channel | | Sort | Updated, priority or created | Manual order, priority, status, title, created, updated or target date | | Saved views | No board view menu | The Issues tab's three-dot menu selects and manages views | The search field shows the label **Search issues**. A search can match an issue key, title or body. Search text narrows the current view; it does not remove its filters. Either can hide an issue from the current result. Grouping divides the same result into sections. Sorting orders that result. Changing either does not change an issue's status or priority. A sortable column header changes the single active sort; other headers are labels. Board filters support multiple values and positive or negative matching. **and** requires all terms to match. **or** requires at least 1 term to match. A board's own-channel scope can remain part of the view without appearing as an editable filter chip. ## Saved and temporary changes The board's saved view supplies its filter, grouping, sort and layout. Your URL can carry changes over that saved view. A dot on the tab marks unsaved view changes. Another reader keeps the saved view until someone saves those changes. The Issues tab's three-dot menu contains its saved views. With editing permission, the menu also offers **New view**, **Rename view**, **Make default view**, view ordering and deletion. **Save as new view** keeps the current changes in a separate view. Resetting the changes returns to the saved view without editing any issue. Search text narrows the current result. Saving a view does not turn its search text into a persistent filter. Filters hold the rules that a saved view retains. ## Issue attributes Attributes appear in the detail pane even when you cannot edit them. A read-only value is not evidence that the issue has no value. A picker becomes available when you can edit the field and its choices have loaded. | Attribute | Behaviour | | --- | --- | | Status | The workflow state picker changes the issue state. The available workflow states appear below. | | Priority | Options are no priority, low, medium, high and urgent. | | Assignee | Options include people and eligible agent destinations. Assigning work to the agent can start a dispatch; choosing a person does not start a coding session. | | Labels | The picker supports multiple labels. Labels can have organisation or workspace scope; equal names can refer to different labels. | | Milestone | The picker offers existing milestones. A new-milestone action requires permission. | | Iteration | The picker offers existing iterations. Creating an iteration from the picker is unavailable. | | Parent | The parent picker searches existing issues. A parent and its sub-issues describe decomposition, not a blocking dependency. | | Type | Read-only classification derived from the title prefix. | | Estimate | Read-only token forecast. The agent supplies the estimate; an absent forecast is not zero. | The exact workflow labels are product strings: **Backlog**, **Todo**, **In progress**, **In review**, **Done** and **Cancelled**. They describe an issue's workflow state rather than a live agent's activity. ## Dependencies and sub-issues **Blocked by** names issues that must precede this issue. **Blocks** names issues that depend on it. The two descriptions refer to the same relationship from opposite sides. Removing that relationship from either side removes it for both issues. The plus control beside either group opens issue search. The remove control on a relation removes that dependency. The list reverts if Crusible refuses the change. Other relation kinds can appear as read-only context; their presence does not imply an editor for every relation kind. Sub-issues belong to a parent. Expanding a parent's sub-issue count shows its children. The child issue's parent field changes where it belongs. A circular parent chain is not a valid hierarchy. ## Comments, replies and activity The detail pane's activity records issue changes and comments. **Leave a comment** opens a new comment. **Reply** opens a reply on an existing comment. Replies have 1 level of nesting. `Enter` posts; `Shift+Enter` inserts a line break. A refused comment keeps your text in the composer. A permission refusal and a failed post are different outcomes: permission requires an access decision; a failed post offers a failure reference. The activity shows accepted comments. A conversation thread and an issue's activity are different places. An issue created from a message retains its source context. The agent's dispatch replies belong to the dispatch's conversation thread. They are not a full copy of its terminal output. ## Dispatch and pull requests **Send to Forge** asks the agent to work on an issue from its conversation card. The assignee picker also offers eligible destinations under **Forge on a Sandbox**. A Sandbox is a coding workspace for this assignment. Saving a draft alone does not send it. An assignment marked **Not started** does not mean the agent is already running. An accepted assignment can wait behind other work. The queue prioritises urgent issues, then high, then medium and no priority together, then low. Within a priority band, arrival order applies unless an authorised manual move changes it. A later priority change can replace that manual ordering. Queue order and a board's manual issue order are separate. A destination can refuse a send, require its owner's consent or have no suitable coding session. The picker offers your own eligible Sandboxes and **Ask to run in their Sandbox** for another person's. That person accepts the request and selects where to run it, or declines it. The request's state remains visible beside the assignment. The dispatch path supports Claude Code, Codex CLI and OpenCode. Other harnesses can appear in machine readings without accepting issue assignments. The picker's unsupported-harness reason is authoritative. Its harness and model tooltip, recent activity and available usage readings help identify the destination. A missing usage reading does not mean zero remaining capacity. A public queue editor and pause control remain planned. The queue's underlying ordering rules do not imply that a board offers those controls. Restarting or powering off the assigned Sandbox can end the active dispatch; those machine actions are separate from removing an issue from a board. Linked pull requests appear under **Pull requests** in the detail pane. Each link opens the proposed change. A link means a pull request exists; it does not mean review, checks or merge have finished. ## Imports, triage and provider boundaries A public CSV/XLSX issue-import workflow, multi-issue bulk editor and dedicated triage queue remain planned. These docs describe no available upload format, column mapping, rejected-row download or bulk confirmation procedure. Individual issue creation and field editing provide the current manual workflow. The agent drafting an issue from a message is available separately from those planned workflows. You review the draft's title, description and attributes before creating it. There is no general issue-field suggestion inbox implied by the Docs surface's suggestion controls. If an issue looks wrong, confirm its key, channel and current board filters. Open the issue's detail pane and compare the differing field with its activity. Include the issue key and field when reporting a discrepancy. A missing issue from a filtered view does not establish that the record is missing.