Skip to content

396 — should check when user have project detail advanced and all tasks ultimate permission

Description

Verifies that an employee with "Project detail advanced" + "All tasks ultimate" project-scoped roles can edit the project's time budget (but not its price budget) on details, and on tasks can edit the time budget while the price budget stays locked — because task price edit needs project-detail-ultimate.

Preconditions

  • A signed-in owner who will create the project role, plus an invited employee who will be added as a member of the first project with that role.
  • Seed data: two projects with budgets and tasks plus one time record per project.

Steps

  1. As the owner, go to Roles → Project roles, add a project role with the test title, toggle "Projects advanced" and "All tasks ultimate" on (project-role flavour), then save. Expected: the new project role exists.
  2. Add the employee to the first project with this role via API. Expected: the API confirms the member with the matching role id.
  3. Reset the session and sign in as the employee. Open the Projects list. Expected: only 1 project is visible.
  4. Inspect the columns. Expected: the time budget column is visible with the API value; the price budget column is hidden.
  5. Open the project and switch to Project details. Expected: the time budget field is editable; the price budget field is locked (read-only).
  6. Open the Tasks tab and enable "Time budget" and "Price budget" via the column manager. Expected: both columns become visible with the seeded values.
  7. Open the task row. Expected: in the task modal the time budget is editable while the price budget is locked (read-only).
  • Spec: playwright/tests/integration/permissions.spec.ts (line 1393)