Project

General

Profile

Actions

roos-fs tasks #821

open

(PROJECT) Introduce New Entity “Team” for Project/Shift Management

Added by Vadim Pariev 5 months ago. Updated 5 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Start date:
11/27/2025
Due date:
% Done:

0%

Estimated time:
18:00 h

Description

Summary
To support upcoming features in project and shift management, we need to introduce a new entity: Team.

Requirements

  1. Create Team Entity

An admin should be able to create a team with the following fields:

  • Name (required)
  • Description (short text, optional)
  • Assigned Users (only users with role Operator)

NOTE
IT might need the role for the Team manager or other implimentation but for now out of scope

  1. Editing & Deleting Teams
  • Admins must be able to edit and delete a team.
  • Only admins have permission to perform these actions.
  1. User Assignment Rules

Only users with the Operator role can be added to a team.

Assignment happens in two places:

  • Team creation/editing screen
  • User creation/editing screen - Operators can be assigned to a team from here as well.
  1. Additional Notes
  • A user may belong to one team.
  • Validation: prevent assigning users with roles other than Operator.
  • When a user is deleted or their role changes, team assignment rules must be removed.
  • Team changes, user assignement are logged in the tema activity log (analog to the user)
  1. List view

The system must include a Teams List View that shows the following information for each team:

  • Team Name
  • Number of Assigned Users (count of operators in the team)
  • Clicking a row should open the team details page.
  • Action items are utilised the same way as other parts of the

The list must support:

  • Pagination or scrolling
  • Sorting by team name, project and etc.
  • Search/filter
Actions

Also available in: Atom PDF