Helpdesk Compatibility Storage

Audience

Developers, database engineers, QA, support and architects.

Summary

Canonical Ticket rows carry an optional positive numeric compatibility identity and metadata used by legacy-shaped API/backfill paths.

Reference Content

A filtered unique tenant/compatibility index protects positive values. Compatibility reads can derive a stable fallback identity when the stored value is not positive. Compatibility create/update maps legacy fields into canonical ticket/category/priority state.

Backfill bypasses global filters, applies explicit tenant predicates, ensures categories/priorities, and upserts by tenant plus compatibility identity. It can preserve valid source metadata or wrap source metadata in structured JSON.

Requires confirmation

Cutover parity, compatibility identity stability, fallback collisions, backfill re-run governance and retirement cleanup require confirmation.

Source References

• microservices/src/helpdesk-service/Domain/HelpdeskEntities.cs
• microservices/src/helpdesk-service/Infrastructure/HelpdeskDbContext.cs
• microservices/src/helpdesk-service/Api/HelpdeskEndpoints.cs
• microservices/src/helpdesk-service/Backfill/HelpdeskBackfill.cs
• microservices/src/helpdesk-service/Infrastructure/Migrations/20260709105542_AddHelpdeskCompatFields.cs

Related Articles

• Database overview
• Schema reference
• Database limitations

See Also

• API documentation
• Technical documentation

Keywords

Compatibility identity, legacy storage, backfill upsert, metadata.

Revision Information

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