Tickets
Tickets as units of work — status, comments, nesting, bulk actions, and archiving.
Tickets
A ticket is the canonical unit of tracked work in ArxDeck. Everything from human tasks to agent runs is anchored on tickets.
What a ticket contains
Each ticket has:
- Title and optional description (markdown with references to docs, knowledge, and other tickets)
- Workflow and status within that workflow
- Assignee, priority, and labels
- Comments and an activity timeline (field changes, archive events)
- Custom fields defined on the ticket's workflow (for example requirements or a technical plan)
- Agent runs and linked pull requests when agents work on the ticket
- Active automated jobs when task templates are running
- Linked tickets (blocker, related, duplicate, follow-up relationships)
- Optional subtickets in a parent/child hierarchy
- Knowledge activity — recent knowledge items referenced or updated in ticket context
Tickets always belong to one project.
Status and workflows
Status is not a single global enum — it comes from the ticket's workflow. Changing workflow on an active ticket is supported for admins and members with edit access, with guards when agents or automated jobs are actively running.
Workflow automations react when status changes, comments are added, or other ticket events occur. See Workflows and Workflow automations.
Comments and activity
The ticket detail page separates:
- Comments — discussion thread
- Activity — field changes and archive/unarchive events
- All — merged timeline
Agent and automation-driven status moves appear in Activity (not as noisy system comments).
Bulk actions
On active ticket lists, users with ticket manage permission can select multiple tickets with checkboxes. A sticky bottom action bar supports:
- Archive, change workflow, change status, change priority, set assignee (active lists)
- Unarchive (archived list)
Saved views support an optional Cost column for project admins (sums all agent runs on the ticket).
Quick add and row actions
The quick-add form above ticket lists creates top-level tickets (title and optional workflow). To add a child ticket, use Create subticket in the row ⋮ menu on the parent ticket.
Row action menus are positioned against the viewport so they are not clipped by the scrollable list; when there is not enough room below, the menu opens upward.
Structured input and agent questions
When an agent calls request_user_input, the ticket shows an inline response form in the comment thread. Users can answer with the visual form or Answer by voice when TTS and STT are available.
Ignore questions dismisses the request and cancels the linked waiting agent run — the form closes and the static question list returns. Dismissed requests do not auto-resume on later comments.
See Voice for voice wizard behavior and Chat & proposals for the proposal flow.
Reset agent context
Users with ticket edit access can Reset agent context from the ticket overflow menu (…). This clears reusable provider context for an agent that has run on the ticket:
- Cancels any active or waiting run for that agent on the ticket
- Ensures the next trigger starts fresh without continuing a prior session
- Historical runs and comments remain visible
Use this when you want a clean agent restart without carrying over prior conversation state.
Nesting and links
- Subtickets — child tickets under a parent; archiving a parent cascades to descendants
- Follow-up tickets — new top-level tickets linked to a source ticket
- Blocker / related / duplicate — directional links between tickets
Knowledge activity
Ticket detail can show a Knowledge activity block with recent knowledge items tied to the ticket. Cross-link to Knowledge base for item history and proposals.
Archiving
Archiving is a soft delete. Archived tickets are hidden from default lists, excluded from automations, and read-only except for unarchive. Members can archive and unarchive according to project permissions.