Fix BACKLOG status dropdown mismatch and related tests

[coderabbitai]

Problem

When a task's current status is BACKLOG, the TaskStatusDropdown component initializes newStatus to BACKLOG, but BACKLOG is excluded from the dropdown options via EXCLUDED_STATUSES. This creates a mismatch where the select element's value doesn't correspond to any available option, resulting in undefined browser behavior.

Tasks

1. Fix the BACKLOG status handling in TaskStatusDropdown component to ensure the select value always matches an available option
2. Update related tests to cover BACKLOG status scenarios

References

• PR: hotfix: show task status dropdown to backlog task status #1391
• Discussion: hotfix: show task status dropdown to backlog task status #1391 (comment)
• File: src/components/tasks/TaskStatusDropdown.tsx
• Requested by: @MayankBansal12

[MayankBansal12]

@coderabbitai can you raise a PR for this issue ticket

[coderabbitai]

Coding Plan

Approach

Fix the TaskStatusDropdown component to properly handle tasks with BACKLOG as their initial status by remapping it to a valid dropdown option, and update tests to cover BACKLOG status scenarios.

Observations

The project is a React/TypeScript application for task management. The TaskStatusDropdown component (src/components/tasks/TaskStatusDropdown.tsx) handles status changes for tasks with validation logic for progress updates. It uses an EXCLUDED_STATUSES array to filter out certain statuses (COMPLETED, BACKLOG, MERGED, UN_ASSIGNED) from the dropdown options. There's already an established pattern for handling excluded statuses that can appear as initial values: COMPLETED is remapped to DONE. Task statuses are defined in src/constants/task-status.ts, and tests are located in __tests__/Unit/Components/Tasks/TaskStatusDropdown.test.tsx.

Assumptions

Assumption 1: What status should BACKLOG be remapped to when it's the initial task status?

Options Considered:

1. ASSIGNED - First status in the active workflow, represents transition from inactive to active work
2. IN_PROGRESS - Represents immediate work starting, but may be too presumptive
3. AVAILABLE - Represents unassigned tasks, but semantically different from BACKLOG intent

Chosen Option: 1

Rationale: This aligns with the codebase pattern where handleAssignToIssueAssignee sets tasks to ASSIGNED when transitioning to active work, and matches agile workflow conventions where backlog items move to "Selected/Assigned" before active development.

💡 User Tips

Regenerate the plan with different choices with @coderabbitai <feedback>.

Implementation Steps

Fix BACKLOG Status Handling and Update Tests

This phase addresses the core issue by adding status remapping logic following the existing COMPLETED→DONE pattern, then updating tests to ensure BACKLOG scenarios are properly covered.

Task 1: Add BACKLOG Status Remapping in TaskStatusDropdown

Add conditional logic to remap BACKLOG to ASSIGNED when initializing the component, following the existing pattern used for COMPLETED→DONE remapping.

• Locate the existing COMPLETED→DONE remapping logic in src/components/tasks/TaskStatusDropdown.tsx (in the TaskStatusSelect component, around line 30-32)
• Add a similar conditional check for BACKLOG status that remaps it to ASSIGNED
• The remapping should occur in the same location as the COMPLETED check, before the select element renders
• Ensure the remapping uses BACKEND_TASK_STATUS.BACKLOG and BACKEND_TASK_STATUS.ASSIGNED constants for consistency

Task 2: Update Tests for BACKLOG Status Scenarios

Enable the currently skipped BACKLOG test and add additional test coverage to verify the remapping behavior works correctly.

• In __tests__/Unit/Components/Tasks/TaskStatusDropdown.test.tsx, locate the skipped test at line 149 (it.skip('should show text Backlog when a task with Backlog status is passed down.'))
• Update this test to verify that when oldStatus is BACKLOG, the dropdown displays "Assigned" as the selected option (not "Backlog")
• Change it.skip to it to enable the test
• Update the test's assertion to check for "Assigned" instead of "Backlog" since BACKLOG will be remapped
• Add an additional test case to verify that changing status from a BACKLOG-initialized task triggers the onChange callback with the correct status value
• Follow existing test patterns using @testing-library/react utilities (render, screen, fireEvent)

🤖 Prompt for AI agents

Fix BACKLOG status handling in TaskStatusDropdown by remapping it to ASSIGNED,
following the existing COMPLETED→DONE pattern. Update tests to verify the
remapping behavior.

In `src/components/tasks/TaskStatusDropdown.tsx`:
- Locate the existing COMPLETED→DONE remapping logic in the TaskStatusSelect
component
- Add a conditional check for BACKLOG status that remaps it to ASSIGNED
- Use `BACKEND_TASK_STATUS.BACKLOG` and `BACKEND_TASK_STATUS.ASSIGNED` constants
- Place the remapping in the same location as the COMPLETED check, before the
select element renders

In `__tests__/Unit/Components/Tasks/TaskStatusDropdown.test.tsx`:
- Enable the skipped BACKLOG test by changing `it.skip` to `it`
- Update the test assertion to verify "Assigned" is displayed (not "Backlog")
- Add test case to verify onChange callback is triggered correctly when status
changes from BACKLOG-initialized task
- Use existing test patterns with `@testing-library/react` utilities

---

🚀 Next Steps

🤖 All AI agent prompts combined

Fix BACKLOG status handling in TaskStatusDropdown by remapping it to ASSIGNED,
following the existing COMPLETED→DONE pattern. Update tests to verify the
remapping behavior.

In `src/components/tasks/TaskStatusDropdown.tsx`:
- Locate the existing COMPLETED→DONE remapping logic in the TaskStatusSelect
component
- Add a conditional check for BACKLOG status that remaps it to ASSIGNED
- Use `BACKEND_TASK_STATUS.BACKLOG` and `BACKEND_TASK_STATUS.ASSIGNED` constants
- Place the remapping in the same location as the COMPLETED check, before the
select element renders

In `__tests__/Unit/Components/Tasks/TaskStatusDropdown.test.tsx`:
- Enable the skipped BACKLOG test by changing `it.skip` to `it`
- Update the test assertion to verify "Assigned" is displayed (not "Backlog")
- Add test case to verify onChange callback is triggered correctly when status
changes from BACKLOG-initialized task
- Use existing test patterns with `@testing-library/react` utilities

💡 Iterate on the plan with: @coderabbitai <feedback>

Example Feedback
- `@coderabbitai` You can skip phase 3. Add a simple unit test case for phase 2.
- `@coderabbitai` For assumption 1 go ahead with option 3 and replan.

---

💬 Have feedback or questions? Drop into our discord!