Create a ticket
File work for a company, set type, priority, visibility, and fields.
From the tickets board, open New ticket (or the equivalent create action).
Steps
- Title — short, customer-safe summary when the ticket may become
public. - Type — e.g. bug, feature, question (configured per workspace).
- Priority and initial status (defaults come from workspace config).
- Company — which end-customer this concerns (e.g. Acme). Often pre-selects the first company.
- Visibility —
internal(default when unsure),public, orrestricted. - Custom fields — type-specific fields (often a rich-text description).
- Assignees / labels — optional at create time; editable later.
- Submit.

Visibility checklist
| Intent | Visibility |
|---|---|
| Team-only planning / triage | internal |
| Share progress with the whole company on the ticket | public |
| Share only with matching end-user attributes | restricted + access rules |
After create
You land on ticket detail. Attach files, leave an internal note for the team, or write the first customer-visible reply if the portal should already show conversation.