Overview
Properties make tickets easier to route and review. Keep them current so list views, kanban groups, filters, and teammate queues stay accurate. Ticket properties appear in several surfaces: the detail metadata panel, table cells, kanban cards, row menus, contextual menus, and command menu actions. Go to Tickets, open a ticket, and use the metadata panel.| Property | Where it appears | Why it matters |
|---|---|---|
| Status | Tables, kanban groups, detail panel | Shows workflow progress. |
| Assignee | Views, rows, detail panel | Determines ownership. |
| Labels | Tables, grouped boards, filters | Categorizes work. |
| Due date | Detail panel and rows | Tracks time-sensitive work. |
| Linked conversations | Detail panel | Keeps customer context attached. |
| Linear/Jira | Detail panel | Connects external execution. |
Ticket properties
Most ticket properties are available from the metadata panel, table cells, kanban cards, menus, or the command menu.Status
Status shows the ticket’s progress through your workflow. Admins can configure ticket statuses from settings. Ticket kanban views can group by status, making status accuracy important for board-based work.Assignee
Assignee shows who owns the next step. Tickets without an assignee appear in the Unassigned tickets view. Assignment can be changed from the detail page, list/table rows, kanban cards, and command menu.Labels
Labels group tickets by topic, priority, customer segment, or workflow. The ticket board can group or subgroup by labels, so labels affect both filtering and layout.Due date
Due dates help track time-sensitive work.Relationships
Tickets become more useful when they stay connected to context.Linked conversations
Linked conversations show the customer thread or internal message that created the work. Use linked conversations for evidence and customer context. Use comments for internal discussion about what to do next.Company
Company context helps teammates understand the account behind the work.Contact
Contact context helps identify the person involved in the request.Related tickets
Related tickets connect separate pieces of work that should be understood together. Related tickets are useful when one customer issue spans several tasks or when duplicate work appears.External links
External links connect Sayless work to other systems.Linear issue
Use Linear links when ticket work continues in Linear.Jira issue
Use Jira links when ticket work continues in Jira.Property changes
Property changes are recorded in activity history.Activity entries
Status, assignee, labels, linked conversations, and related ticket changes can appear as activity entries.Bulk updates
Some properties can be changed for multiple selected tickets from table or kanban views, depending on the action and permissions.Kanban grouping uses ticket properties. If a ticket appears in the wrong group, check the property used by the current board grouping.