One of the quiet benefits of tickets being ordinary work items is that you don't need a separate reporting tool for support. Every place you already filter, sort, save views, and report on items understands tickets too.
Across the app's item tables and filter bars, a Support filter lets you narrow to tickets (or exclude them). Use it to answer questions like "show me only support work" on a shared board, or "hide tickets" when you want to look at delivery work on its own.
The Service Desk Inbox applies this automatically — it's permanently scoped to tickets — but the Support filter is available elsewhere so you can slice support work into any view.
When you're looking at tickets, the filter bar adds support-specific dimensions on top of the usual ones (owner, status, priority, dates, labels, custom fields):
Combine these with the standard filters to build precise queries — "open tickets from Acme, unassigned, raised this week," for example.
Add support columns to your item tables to see the information that matters for triage — the requester and company alongside status, owner, and priority — so a queue reads at a glance.
Capture any filtered, sorted, columned setup as a saved view and reuse it, or share it with teammates — exactly as you would for any items view. A few that teams find useful:
The Suspended Queue
Some inbound mail is held back for safety instead of becoming a ticket. The Suspended tab is where you review it and decide: recover or drop.
Permissions
Service Desk access is governed by roles, just like the rest of DevStride. Four permissions control who can configure the desk, manage requesters, reply to customers, and reach the module at all — and explain why the module or a button can disappear.