Helpdesk Queries

Audience

Developers, QA, support and architects.

Summary

No standalone query classes or mediator were found. Endpoint handlers compose EF Core queries and project directly into API records.

Reference Content

Ticket list/detail, attachment list/download, categories, priorities, SLA policies, audit, timeline, outbox, compatibility records and four reports are verified query surfaces. Read-only paths frequently use no-tracking queries; detail includes assignment, comment and attachment collections.

Global tenant filters provide tenant scope. The canonical ticket list has no requester parameter, pagination or server-side search/filter contract. The employee gateway forwards that list unchanged, while admin search and filtering occur in the browser.

Requires confirmation

Pagination, requester scoping, query authorization, stable sorting, report time ranges and read-model separation require confirmation.

Source References

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

Related Articles

• Technical overview
• Technical limitations
• Helpdesk business documentation

See Also

• Technical source map
• Architecture overview

Keywords

Helpdesk queries, EF Core projection, report query, requester scope.

Revision Information

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