Skip to content

393 — should check when user have project detail advanced permission

Description

Verifies that an employee with the "Project detail advanced" project-scoped role on a single project can see and edit the project's time budget and view (read-only) the price budget on details, but the project list still hides the price column and task budgets stay locked.

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" on (project-role flavour), then save. Expected: the new project role exists.
  2. Add the employee to the first project with the new 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 (the project the employee was added to).
  4. Inspect the columns. Expected: the time budget column is visible with the API value; the price budget column is hidden (the project list price column requires the global Price budgets permission).
  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" in the column manager. Expected: both columns become visible with the seeded values.
  7. Open the task row. Expected: in the task modal both budgets are locked (only project-detail-ultimate would unlock task budgets).
  • Spec: playwright/tests/integration/permissions.spec.ts (line 1191)