Roos-fs-ZIP

General
Task is a piece of work that is normally done in the frames of the service.
Worst case scenario the car would be have 200 tasks per service.
Since task is created and saved like a tempate it needs to be created by the admin in a seperate area.

Acceptance criterea

• seperate area to manage tasks exists (table with the tasks)
• Admin user can create a new task manage existing tasks

Properties and their picularities for the Tasks:
Name
Text field

Description
Text field

Price
Numeric field with the currency symbol (euro)

This field is to be entered and to be seen manually from the ADMIN user¶

This field is to be seen only by the ADMIN¶

This field is only available for the Customer user if the SERVICE in the COMPLETED STATE¶

Employee is under any surcamstances is not allowed to see this field

Duration (estimated tme)
Numeric field showing how much time the task would take to execute
(see status ticket for the )

Customer
Dropdown
Entries are taken from the existing customer (created by the admin)

Status
See State machine Ticket

Other
The tasks could be assigned to the service (from a template list)

Expected flow

Employee logs in to the application
navigates to the car list
selects a car of interest
in the car data he/she sees the list of services (in case no services are created yet the user sees the message that there are no services yet created for the vechicle)
Employee can enter the service
Employee can edit the service and add new tasks from the dropdown list
Same flow is applicable for the admin

Out of scope for the ticket

status
change status actions
check lists