A queue that reads like a column
Status, priority, SLA, owner — every column tabular, every row scannable. Bulk actions without the dropdown maze.
The ticket workspace is the heart of Reqdesk. It looks like a list because most of the time, that is what you need — a tabular column you can scan, sort, and reach into. The same dataset becomes a board when you need to see what is in flight, a table when you need to compare across columns, and a timeline when you need to understand what happened in what order.
What you get
- Four views, one dataset. Switch between list, board, table, and timeline without losing your filtered slice. Each view remembers its own sort order so you can keep them tuned.
- Tabular columns. Status, priority, SLA, owner, age, last reply — every numeric value tabular-aligned for fast scanning, every status pill consistent across views.
- Bulk actions. Select a hundred tickets, set their owner, change their status, apply a tag — without a dropdown maze. Every bulk action is one row in the audit log.
- Saved slices. A filter is a URL. Send it, bookmark it, share it, embed it in a Notion doc. No “saved view” dance.
Replies, attachments, and the audit log
Every ticket carries its full reply thread, every attachment, and an append-only audit log of who changed what and when. Workspace owners can export the audit log at any time — you do not have to ask us.
Why it reads like a ledger
Because that is what a ticket queue is — a ledger. It is what you wrote down, in the order you wrote it, with running totals (open, in-flight, resolved) at the side. We chose tabular numerals, monospace metadata, and a strictly hierarchical layout so your eye lands where it expects to.