Skip to content

575 — should create new task and assert edit values

Description

Verifies that after creating a task with every field populated (title, description, project, assignee, story points, priority, sprint, start and due dates), trashing it, and restoring it, all original field values are preserved exactly when the task is reopened.

Preconditions

  • Signed-in admin owner of a fresh organization with a seeded project and one existing task.
  • A sprint of one-week duration has been created on the project via API.

Steps

  1. Open the seeded project's Tasks tab and click "Add task". Expected: The task creation modal opens.
  2. Fill the form: title (random 4 words), description (random sentence), project (the seeded project — selected first so Assignee/Reporter/Sprint fields appear), assignee (owner), story points (random 1–20), priority "Lowest", sprint (the created sprint), start date (today −5 days), due date (today +5 days), then click "Create". Expected: "Created" toast appears and the Tasks tab now shows 2 tasks.
  3. Move the new task to trash and confirm the modal. Expected: "Moved to trash" toast appears.
  4. Open the Trash page. Expected: Exactly 1 item is listed — the new task, type "Task", owner name, today's date.
  5. Trigger "Restore all". Expected: Trash empties.
  6. Re-open the project's Tasks tab and click the restored task. Expected: The edit modal opens and shows the original title, description, project, status "To Do", assignee, reporter (owner), story points, priority "Lowest", sprint title, start date (today −5), and due date (today +5) — all preserved.
  • Spec: playwright/tests/integration/trash.spec.ts (line 173)