Helpdesk Employee Self-Service
Employee journey
Implemented experience
The page provides text inputs for title, description, category and priority. Category defaults to IT and priority to Low. It validates only that title and description are nonempty. The history table attempts to show title, category, priority, status and due date and provides an empty state when no rows are returned.
The employee dashboard separately counts non-resolved/non-closed rows returned by its Helpdesk source.
Material gaps
The form sends category and priority names, but the canonical service contract requires category and priority GUIDs. It also does not send requester fields, although the service can fall back to tenant context for those values. The gateway forwards the request body unchanged.
The ESS list forwards to the tenant ticket collection without a requester filter. The resulting history and dashboard count are tenant-wide rather than verified self-only data. The page obtains a load error from its hook but does not render it, and submission errors are not caught locally.
No employee detail, comment, attachment or cancellation UI exists.
Source References
UI/salary-ui/apps/client-hrms-portal/src/ess/EssPages.tsxUI/salary-ui/apps/client-hrms-portal/src/ess/essApi.tsmicroservices/src/gateway-api/EssEndpoints.csmicroservices/src/helpdesk-service/Api/HelpdeskEndpoints.cs
Related Articles
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.