You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implement repository interfaces and CRUD handlers for the Status, Category, and Comment models to complete the core data persistence and API endpoint coverage for Sprint 1.
Motivation
Parity with Issues: Status, Category, and Comment models need the same CRUD operations (Create, Read, Update, Delete/Archive)
API Completeness: Enable full REST API coverage for issue metadata management
Vertical Slice Pattern: Each model should follow the same handler + repository + validator structure as Issues
Soft-Delete Consistency: Comment and other models should support archiving (IsArchived) for consistency
Scope
Models to implement handlers for:
Status - Issue status options (Open, In Progress, Closed, etc.)
Category - Issue categorization/tagging
Comment - Comments on issues (with soft-delete support)
Objective
Implement repository interfaces and CRUD handlers for the Status, Category, and Comment models to complete the core data persistence and API endpoint coverage for Sprint 1.
Motivation
Scope
Models to implement handlers for:
Deliverables per model:
Repository Interface (\IStatusRepository, \ICategoryRepository, \ICommentRepository)
CRUD Handlers (following existing Issue handler pattern)
CQRS Queries & Commands
API Endpoint Registration (in \Program.cs)
Folder Structure (depends on [Refactor] Reorganize Handlers folder by model domain #32)
Acceptance Criteria
Dependencies
Notes
Related Issues