Skip to content

479 — should create new task and assert edit values

Description

Verifies that a freshly created task, when reopened in the edit form, preserves every value the user originally entered — confirming both create-side persistence and edit-form prefill behavior.

Preconditions

  • Signed-in tenant with a seeded Advanced project, a one-week sprint, an employee, and three labels.
  • Currently on the seeded project's Tasks tab. Assignee/Reporter/Sprint fields appear in the form because it is opened from within a project.

Steps

  1. Click "Add task" and fill in title (random 4-word string), description, assignee (current owner), story points (random 1–20), priority "Lowest", the seeded sprint, and three labels.
  2. Pick the start date (today − 5 days) and due date (today + 5 days).
  3. Click "Create" → Expected: the "Created" success toast appears and the grid shows exactly 1 task.
  4. Click the new task row to reopen it in the edit form.
  5. Inspect every field → Expected: title, description, project (seeded project), status "To do", assignee and reporter (current owner), story points, priority "Lowest", sprint, start date (today − 5d), and due date (today + 5d) all match what was entered, and the labels chip count matches the three labels.
  • Spec: playwright/tests/integration/task.spec.ts (line 170)