Skip to content

088 — Should move task to different statuses, and then change status

Description

Verifies that remapping the IN PROGRESS column to a different status ("TEST IN PROGRESS") leaves tasks that were previously IN PROGRESS off the board — because their status no longer matches any visible column — while tasks in other columns remain.

Preconditions

  • Signed-in user on a freshly registered organization.
  • An advanced-type project with 5 tasks in an active sprint "Started Sprint".
  • The task workflow has 5 statuses.
  • The Agile Board view is open and shows 5 tasks in TO DO.

Steps

  1. Drag task2 and task3 into DONE, and task4 and task5 into IN PROGRESS. Expected: TO DO has task1 (count 1); IN PROGRESS has task4, task5 (count 2); DONE has task2, task3 (count 2); column order is TO DO → IN PROGRESS → DONE.
  2. Open Board Settings. Expected: 4 columns visible.
  3. Move the IN PROGRESS status into the Unmapped area, then drag the "TEST IN PROGRESS" status into the IN PROGRESS column. Expected: the IN PROGRESS column is now mapped to "TEST IN PROGRESS"; the Unmapped area contains "TEST TODO" and IN PROGRESS; 4 columns total.
  4. Save settings. Expected: a "saved" confirmation appears.
  5. Return to the Agile Board. Expected: TO DO shows task1 (count 1); IN PROGRESS is empty (count 0) because task4 and task5 still have status IN PROGRESS — which is no longer mapped to any column; DONE still shows task2 and task3 (count 2); total visible tasks on board = 3; column order is TO DO → IN PROGRESS → DONE.
  • Spec: playwright/tests/integration/board.spec.ts (line 771)