Skip to main content

Helpdesk Technical Limitations

Audience​

Developers, product, QA, security, support and architects.

Summary​

The extracted capability is Transitional. The following limitations are verified and must not be presented as implemented controls.

Reference Content​

Architecture​

  • Endpoint handlers combine transport, orchestration and persistence concerns.
  • Layer boundaries are folders within one assembly.
  • No background SLA-check registration is visible.

Ticket lifecycle​

  • Generic status change has no transition matrix and can bypass dedicated timestamp behavior.
  • Mutable entities do not encapsulate most lifecycle invariants.

Assignment​

  • No employee-directory resolution, agent eligibility validation, queue/team model or concurrency control is verified.

Integration​

  • Document calls are outside the relational transaction; local deletion does not delete external content.
  • Employee create payload and canonical category/priority identifier contract differ.
  • Employee listing is tenant-wide rather than requester-filtered.

Validation​

  • Validation is distributed and no dedicated validator framework/classes exist.
  • Assignee identity and internal-comment privilege are not service-validated.

Authorization​

  • Direct service startup has no verified authentication/authorization middleware or endpoint policy.
  • UI role/permission checks are presentation controls only.
  • Forwarded identity/tenant headers need a confirmed trust boundary.

Compatibility​

  • Legacy and canonical routes/models coexist.
  • Employee-service routing directly targets the extracted service while administrative routing is switchable.
  • Backfill parity validates counts/groupings, not full semantic equivalence.

Testing​

  • No dedicated Helpdesk unit, integration or frontend automated tests were found.
  • Backfill smoke/validation tooling does not cover runtime security or lifecycle behavior.

Requires confirmation​

Owners must confirm which limitations block production release, remediation sequence, accepted residual risk and compatibility exit criteria.

Source References​

  • microservices/src/helpdesk-service/Program.cs
  • microservices/src/helpdesk-service/Api/HelpdeskEndpoints.cs
  • microservices/src/helpdesk-service/Infrastructure/DocumentServiceClient.cs
  • microservices/src/gateway-api/EssEndpoints.cs
  • UI/salary-ui/apps/client-hrms-portal/src/ess/EssPages.tsx

See Also​

Keywords​

Helpdesk limitations, architecture gap, authorization gap, validation gap, test gap.

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Next review: 2026-10-20