- Tickets, a small support desk: customers send tickets from a project's form (
/my/object-createlogged in,/public/object-createwithout a login), with theirname,emailandmobilekept on the ticket;ticketgetspriority(Low, Normal, High),closed_at(set by a trigger when the status becomes Closed) and three statuses, Open, In Progress, Closed (from 18.0.0's five; no project had tickets yet). The 18.0.0 columnreplyis no longer used (Atom keeps columns it doesn't manage; it stays empty) (docs/crud.md). - Ticket comments: a new table
ticket_comment, the team's notes on a ticket in Markdown, with its own permissions (create 123, read 124, update 125 and delete 126 anyone's; an author edits and deletes their own through/my); deleting a ticket deletes its comments./my/object-createrefusesticket_comment. - The Tickets page, in the apps' look: a board (Open, In Progress, Closed; drag a card to change its status) or a table, filters (status, priority, type, source, created) and a search (title, name, email, mobile, ID), the ticket detail with the contact and the comments, Add ticket, CSV export. Ticket read (120) opens it: any other user is told "Tickets access is unavailable.". Built for millions of tickets: one statement for the board's first pages, cursor paging everywhere, no counts, an index for every filter and search.
/permission/object-readreads a board:group_columnandgroup_values(the first page of each value in one statement), as/private/object-read.