Helpdesk Development Seeding

Audience

Developers, QA, support and DevOps.

Summary

One static seeder runs only from the Development startup path after migration application.

Reference Content

The seeder checks for an existing marker category in one fixed development tenant and exits when found. Otherwise it inserts four example categories, four priorities, four Resolution SLA policies, three sample tickets, one assignment, one comment and one audit row, then saves once.

Seed values are development examples, not production taxonomy, SLAs or personal data. This documentation intentionally omits the fixed tenant and sample identity values.

Requires confirmation

Test-environment ownership, repeatability after partial seed, sample-data cleanup and whether automatic seeding remains enabled require confirmation.

Source References

• microservices/src/helpdesk-service/Infrastructure/DevelopmentSeeder.cs
• microservices/src/helpdesk-service/Program.cs
• microservices/src/helpdesk-service/Domain/HelpdeskEntities.cs

Related Articles

• Database overview
• Schema reference
• Database limitations

See Also

• API documentation
• Technical documentation

Keywords

Development seeder, sample data, idempotent marker, startup.

Revision Information

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