Skip to content

Release v4.51.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 16 Oct 06:00
v4.51.0
02edf81
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

The Ticketing / Helpdesk domain blueprint of Part B 3.2 of the screen blueprints specification, shaped like the CRM blueprint.

Added

  • @cratis/scene.blueprint.ticketing, a blueprint package (domain ticketing, category Business / Ticketing): nine screen templates, six dialog templates and nine ready-to-use screens.
    • SupportDashboard: open tickets, overdue and the average first response; open tickets by priority and by assignee; the overdue tickets; my next steps.
    • TicketQueue (id, subject, requester, priority and status chips, assignee, age; saved views Unassigned, Mine and Overdue), MyTickets and CustomerList.
    • TicketBoard: a column for each status with a card for each ticket.
    • TicketPage: the conversation as the page's activity, the properties in the aside, and the quick actions Assign, Change status, Escalate and Merge, each opening its dialog.
    • TicketCreateForm and the public-facing TicketPortalForm (full-page layout, no application chrome, a notice about what happens next, only what a customer can say).
    • KnowledgeBase: a search box and a tree of categories and articles beside the chosen article; a navigation stack on a phone.
    • Dialogs TicketQuickCreate, CustomerQuickCreate, AssignTicket, ChangeTicketStatus, EscalateTicket and MergeTickets.
  • Navigation: a topbar naming the support module and the module's sidebar (Dashboard, Queue with List and Board, My tickets, Customers, Knowledge base), the application structure and ticketingApplication().
  • Sample-data packs ticketing-helpdesk (en-GB) and ticketing-service-desk-de (de-DE) answering the same shapes.
  • Specifications: definition of done per template and package, screen set consistency, applicability by level, every screen previewed in both packs with no accessibility violation, standard states forced on seven screens, the behaviors of the application (quick create, open a ticket, the four quick actions, board moves, the portal form without chrome), and a Chromium audit of every screen and dialog at desktop, tablet and phone widths in light and dark themes (92 specs, in CI).
  • Docs: blueprints/ticketing-blueprint.md.

Fixed

  • The page header of the foundation shell no longer overflows a phone when it carries several actions: the header and its action row wrap (found by the Chromium audit of the ticket page's four quick actions).

Part of #111

Assets 2
Loading