Skip to main content

Helpdesk Ticket Details

Implemented detail panel

Selecting Detail stores the queue row and opens a panel on the same page. It displays status, category, priority, requester, assignee, due/opened/updated dates, assignment controls, internal-comment input and a separately loaded attachment table.

There is no route parameter, bookmarkable detail URL, close control, timeline display, comment history, assignment history or full description field in the panel.

Contract mismatch

After a mutation, the UI requests canonical ticket detail and stores the response directly as the selected row. The service returns TicketDetailDto with nested ticket, assignments, comments and attachments; the UI reads top-level ticket properties. Fields can therefore fall back to placeholders, and subsequent attachment loading can lose the ticket identifier.

Although the service supplies comment, assignment and attachment collections inside the detail response, this screen neither unwraps nor renders those collections. It performs a separate attachment-list request instead.

Classification

The detail experience is Partial/Transitional and requires frontend/backend contract alignment before it can be treated as reliable.

Source References

  • UI/salary-ui/apps/client-hrms-portal/src/pages/admin/OperationsAdminPages.tsx
  • microservices/src/helpdesk-service/Api/HelpdeskEndpoints.cs

See Also

Keywords

Helpdesk, employee service desk, ticket UI, operations, diagnostics.

Revision Information

Draft source-backed documentation reviewed on 2026-07-20; next quarterly review is 2026-10-20.