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.
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.
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. |
| 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.
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.
Capture any filtered, sorted, columned setup as a saved view, for yourself or shared with teammates, exactly as for any items view. Useful ones:
Held for Review and Rejected Mail
Some inbound mail is held back instead of becoming a ticket or an article reply. Review what was held and why on the Held for review tab, recover real messages, and use Rejected mail to answer 'did this email reach us?'
Service Level Agreements (SLA)
Promise how fast your team responds to and resolves tickets, have DevStride track the clock against your business hours, pause it while you wait on the customer, and get warned or reply automatically before a promise is missed.