Finding & Filtering Tickets
Tickets are work items, so every items table, filter, and saved view understands them. The Support filter, the ticket dimensions (requester, company, channel, importance), the ticket columns, and the views worth saving.
On this page
Because tickets are ordinary work items, you don't need a separate tool to find or report on support work. Every place you filter, sort, and save views understands tickets.
Scope to tickets: the Support filter#
In any filter bar, the Support filter narrows to tickets or excludes them. Use it to show only support work on a shared board, or to hide tickets when you want delivery work on its own. The Service Desk Inbox applies it permanently as the Tickets only pill.
Filter by ticket dimensions#
On top of the usual filters (owner, status, priority, dates, labels, custom fields), ticket filters add:
| Filter | Use it to |
|---|---|
| Requester | Narrow to one customer, or switch on Is not to leave out the tickets from the requesters you pick. Is not works in the Inbox too, alongside its Tickets only pill. |
| Company | See everything from one customer organization. |
| Channel | Filter by how the request arrived: Email, Portal, or API. |
| Importance | Narrow to tickets marked Critical, Important, or Nice to have. |
All of them are also in the advanced condition builder, so they can go into any complex saved view: open, Critical tickets from Acme, unassigned, raised this week.
Ticket columns#
Add ticket columns from the column picker on any items table. A table with no saved layout shows them by default; a saved view adds them from the picker:
| Column | What it shows |
|---|---|
| Requester / Company | Who asked, and for which customer. |
| Channel | How it arrived. |
| Importance | The customer-importance level. Click the cell to set it. |
| Customer Rank | A Ranked marker on tickets the customer has ordered. Sort by this column to see the order. |
| SLA Due | When the nearest SLA target falls, with overdue tickets flagged. |
| First Response | When the ticket first received a public reply; blank until then. |
| Service Desk | A compact card combining the requester, company, and importance. |
Importance, Customer Rank, SLA Due, and First Response are sortable. Sorting by SLA Due is the fastest "what's about to breach" queue; sorting by Importance or Customer Rank puts the customer's highest-value work first. For a live list of running SLA timers, use the SLA at risk tab instead.
Save and share views#
Capture any filtered, sorted, columned setup as a saved view, for yourself or shared with teammates, exactly as for any items view. Useful ones:
- Unassigned (seeded in the Inbox): what still needs an owner.
- My open tickets: your personal queue.
- One company's requests: for an account review.
- Critical, no reply yet: Importance is Critical, First Response is empty.
Report on support like any work
Service Desk has its own Reports tab with six support reports. And because tickets flow through boards and cycles like other items, your existing reports (throughput, cycle time, cumulative flow) work on support too; filter a report to tickets with the Support filter. See Measure Performance: Reports.