Skip to content

Help Topics

Help Topics are tenant-defined classifications that the create form uses to pre-fill ticket properties. Selecting a topic on Create Ticket auto-fills the priority, queue, assignee, and computed due date, so common request types can be opened with a single click.

Help Topics admin list page with active and inactive topics

  • Route: /service-desk/admin/help-topics
  • Menu path: Service Desk → Settings → Help Topics
  • Primary audience: Admins (service-desk.admin).
FieldRequiredTypeDescription
NameYesTextDisplay name shown in the create-form dropdown
CodeYesTextShort identifier; referenced by integrations
DescriptionNoTextAuthor-facing notes about when to pick this topic
Default priorityNoSelectlow, medium, high, urgent
Default queueNoQueue selectorOverrides routing rules — tickets with this topic always land in this queue
Default assigneeNoUser selectorForces direct assignment to a specific agent
Default due offset (hours)NoNumberNumber of hours from create time used to compute due_at
ActiveNoToggleInactive topics hide from the create-form selector but keep their existing tickets
FilterTypeDescription
SearchFree textMatches name and code
Show inactiveToggleIncludes deactivated topics in the list
ActionPermissionDescription
New Topicservice-desk.adminOpens the create dialog
Editservice-desk.adminEdit any field; changes are not retroactively applied to existing tickets
Deleteservice-desk.adminThe ticket’s help_topic_id is set to NULL (ON DELETE SET NULL) — existing tickets keep their other field values
  • Help-topic defaults apply only at create time. Editing a topic afterwards does not retroactively change tickets already created against it.
  • A topic’s default_queue_id overrides the queue selected by routing rules — a routing rule with assign_to_queue will still run, but the help topic wins the final queue. Use this when a topic always belongs to a specific specialist group.
  • Inactive topics remain attached to their historical tickets (the help_topic_id foreign key is preserved). They simply disappear from the create-form selector.
  • The default due offset is in hours; for SLA targets in days, multiply (e.g. 48 = two business days, but note SLA math is wall-clock, not business hours).
  • Create Ticket — the form that consumes these defaults.
  • Queues — the queue routed to when no topic-level queue override is set.
  • Settings — tenant-wide default priority and SLA target hours used when a topic does not override.