Skip to main content

Helpdesk Priority Endpoints

Audience​

Developers, QA, support and architects.

Summary​

The canonical priority surface supports tenant-visible listing and creation.

Reference Content​

Listing sorts by rank and returns identity, name, level, rank and active state. Creation requires a nonblank name, defaults an unknown/missing level to Medium, changes a nonpositive rank to one, defaults active state to true and writes audit.

No canonical priority update, deactivate or delete operation exists. Compatibility requests may create missing priorities from supplied text.

Requires confirmation​

Priority administration authorization, rank constraints, strict enum validation, duplicate handling and retirement behavior require confirmation.

Source References​

  • microservices/src/helpdesk-service/Api/HelpdeskEndpoints.cs
  • microservices/src/helpdesk-service/Infrastructure/HelpdeskDbContext.cs

See Also​

Keywords​

Priority API, rank, priority level, reference data.

Revision Information​

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