Project

General

Profile

roos-fs tasks #840

Updated by Vadim Pariev 5 months ago

On the left side of the planning view, users should see a section listing all services available for planning. 
 These services originate from projects that already exist in the system adn the location the user has selected.  

 system. 

 The services displayed must dynamically update based on the selected team, project, and location, following specific filtering logic. 

 **Business Rules and Logic** 
 1. Source of Services 

 * Every service (shown in the list) belongs to a vechicle that is assigned to a location. project. 
 * When a location team is selected, the system should automatically show only services from the project(s) assigned to that location (through the vechicles). team. 

 2. Project-Based Team-Based Filtering 

 * as soon as the location If Team A is selected we need assigned to one project → show only services belonging to that single project. 
 * If Team B is assigned to multiple projects (e.g., 3 projects) → show services belonging to all three projects. 
 * The team selection is therefore the user that first-level filter. 
 * On default there are no services from different projects 
 Like: 
 Bettery check 10/49 (ALready planned shown  
 * In case there are not services in the status other locations/planned then completed for the week - the last value is take from the ,anual input plan from the porjet menegement area) 
 Wheel exchange 49/49 project render "no open services are present for this project" 

 3. Additional Filtering Options 

 * Users can manually filter services by selecting a specific project. 
 * When a project is selected, the list should show only services belonging to that project (optionally combined with a location filter—see below). 
 * Filtering by Location 
 * Users can filter services by location. 
 * Locations and projects are structured hierarchically. 

 4. Hierarchical Filtering Logic 

 Case A: Location selected first 

 User selects a location. 
 System limits available services to only those belonging to this location. 
 When the user selects a project, the service list shows services filtered: 

 * First by location 
 * Then by project 

 Case B: Project selected first 

 User selects a project. 
 System shows all services belonging to that project. 
 When the user selects a location, the service list is filtered further: 

 4. * First by project 
 * Then by location 

 The filtering is always applied in the order the user selects the filters. 

 5. Service List Content (What must be shown) 

 Each service entry must display: 
 * Service ID (unique identifier) 
 * VIN number 
 * License plate 
 * Vechicle Service status (e.g., planned, in progress, pending, completed) 
 * Location 
 * Project 

 UX requirements. it shall be easily distinguishable what location and project this service belongs to.  

Back