Helpdesk Query Patterns

Audience

Developers, database engineers, QA and support.

API handlers and backfill code compose EF Core queries directly; no repository/query-object layer exists.

Ticket list/detail uses no-tracking queries and includes assignment, comment and attachment children.
Employee history forwards the same tenant ticket list; no requester predicate exists.
Assignment/comment/attachment history is ordered or indexed by ticket and creation time.
Attachment download selects by ticket and attachment identity.
SLA checks filter unbreached/unmet due rows and join active assigned tickets.
Audit/timeline/outbox diagnostics order by occurrence and clamp result count.
Dashboard loads tenant ticket rows and separate SLA breach identities.
SLA reporting joins SLA, ticket and policy data; agent/category reports group in memory after loading rows.
Compatibility list loads joined rows before applying optional filters and result cap.

Pagination, requester filtering, server-side report grouping, query plans, memory bounds and diagnostic authorization require confirmation.

EF Core query, ticket retrieval, report query, SLA query, history.