Overview
Tickets are created from Support → New Ticket or via email-to-ticket (if configured).
Highlights
- Fill in the subject, description, priority (Low/Medium/High/Critical), assignee, and linked client.
- Reply to tickets in the Support inbox; toggle Internal Note to write notes visible only to your team.
- Clients receive email notifications of replies.
- Each ticket shows an SLA timer; amber warning means approaching breach, red means breached.
- Configure SLA rules in Settings → Support → SLA Policies.
- Change ticket status from the row menu: In Progress, Send to review, Pending, Close, or Spam. Closed tickets can be reopened.
- Create self-service knowledge base articles at Support → Knowledge Base and link them to tickets.
Log time on a ticket
For: the ticket’s assignee and support staff. You do not need the support role if you are the assignee. Time is booked to the ticket’s project, so the ticket must have a project before time can be logged.
Set the project
Log the time
Ticket hours appear in the project’s time report (group by Ticket, or filter by ticket), in the project’s budget, and in the Support tab summary.
A closed or spam ticket takes no new time. Reopen it first. A week locked by a timesheet approval also blocks entries, as it does for tasks.
Review and close a ticket
For: assignees, reviewers, and managers. Closing a ticket that is in review is limited to its reviewer, a manager, an admin, or an owner.
Assign the ticket
Choose a reviewer
Send to review
Review and decide
A ticket can be closed directly from In Progress without a review. Only the step from In Review to Closed is restricted.