Roos-fs-ZIP

General
Use case - as soon as the service is created and get some tasks assigned and is set to be in the statis OPEN the work of the technician or other person begins (all tasks are now opened). That means that a first person FROM THE WEB APP goes into the service and sees all opened tasks, selects the first one (normally contact the customer or the vechicle user) and presses the button set to in progress, after the communication is done this user sets the locations, tech specialists and the dates for the other tasks. In addition this user goes through his/her instructions filling out all the required fields there. As soon as everything is done the tasks could be completed in the WEB APPLICATION. The same user can enter this task later and see what records were made their what comments were left.

Acceptance criterea

• When a service is in OPEN/BOOKED/COMPLETED status, users can access the list of all tasks assigned to that service
• Tasks in the OPEN/IN PROGRESS/COMPLATED state are clearly listed and selectable from the service detail view.
• User can select an individual task from the list.
• A “Set to In Progress” button is available and only visible for tasks in the OPEN state.
• Clicking “Set to In Progress” updates the task status accordingly and logs the timestamp and user ID.
• A “cancell the task” button is available and only visible for tasks in the OPEN/IN PROGRESS state. In the vent f clicking user is romted to define the reason (by customer or internally) and is requested to provide a textual explanation.
• the user can do following with the task (only if the SERVICE in the OPENED/BOOKED STATE):
  -- Set the planned date
  -- Fill out a predefined instruction checklist/form (with mandatory fields highlighted)

• Form validations are enforced before allowing the task to be marked as completed
• After filling in all required fields, the user can mark the task as completed.
• Completed tasks store:
• Audit trail of field updates
• Timestamps
• Comments left
• Responsible user
• Completed tasks remain accessible from the same service
• When reopening (not the status) a completed task, the user can:
  -- View previously filled data
  -- See all comments and internal logs
  -- Not edit fields unless task is explicitly reopened (in this case as a status) by an authorized role
  -- Task view has a clear separation between read-only history and editable fields.
  -- Each step in the workflow (open → in progress → complete) is clearly indicated visually.
• Error messages and success notifications are shown as needed during state changes or validations.