Summary
CreateIssuePage.razor wires up IssueForm correctly — the form collects Title, Description, CategoryId, and StatusId. However, the submit handler builds CreateIssueCommand with only Title and Description, silently dropping the selected category and status.
Root Cause
// CreateIssuePage.razor — HandleSubmit
var command = new CreateIssueCommand
{
Title = request.Title,
Description = request.Description
// CategoryId and StatusId are missing!
};The CreateIssueCommand may already have CategoryId/StatusId fields — they're just not being set from the form model.
Work Required
- Inspect
CreateIssueCommand record to confirm it has CategoryId and StatusId properties
- Update
HandleSubmit in CreateIssuePage.razor to pass request.CategoryId and request.StatusId
- If the command is missing those fields, add them and update
CreateIssueHandler to apply them
- Validate that a created issue reflects the selected category and status in the detail page
Acceptance Criteria
Files
src/Web/Components/Features/Issues/CreateIssuePage.razorsrc/Api/Handlers/Issues/CreateIssueHandler.cssrc/Shared/ (CreateIssueCommand definition)
Summary
CreateIssuePage.razorwires upIssueFormcorrectly — the form collectsTitle,Description,CategoryId, andStatusId. However, the submit handler buildsCreateIssueCommandwith onlyTitleandDescription, silently dropping the selected category and status.Root Cause
The
CreateIssueCommandmay already haveCategoryId/StatusIdfields — they're just not being set from the form model.Work Required
CreateIssueCommandrecord to confirm it hasCategoryIdandStatusIdpropertiesHandleSubmitinCreateIssuePage.razorto passrequest.CategoryIdandrequest.StatusIdCreateIssueHandlerto apply themAcceptance Criteria
Files
src/Web/Components/Features/Issues/CreateIssuePage.razorsrc/Api/Handlers/Issues/CreateIssueHandler.cssrc/Shared/(CreateIssueCommand definition)