roos-fs tasks #414
Updated by Vadim Pariev 8 months ago
**General** A complete overhaul of the system of statuses is to be performed. including the Services and tasks. **Current state** <img style="width: 1278px;" src="clipboard-202509132257-tphze.png"><br> **Expected result** <img style="width: 1363px;" src="clipboard-202509182201-obe8x.png"><br> SERVICES adn TASKS FLOW desciption - the service when created receives the status CREATED - the tasks in this service receive the state CREATED - the service is then manually transferred to the stated BOOKED (the user is OBLIGED to set the date - it is mandatory. P.S. reuse the same form that was used for the task when set to the boked state) <img style="width: 432px;" src="clipboard-202509182203-pp09q.png"><br> 547px;" src="clipboard-202509132308-foywh.png"><br> - the tasks are AUTOMATICALLY change the status to OPEN - from the OPEN state the user can set the planned date (OPTIONALLY) - from the OPEN state with or without a date the user can set the task in status IN PROGRESS - from IN PROGRESS the tasks can be set to COMPLETED - the service could be set to COMPLETED only if all Tasks are in CANCELLED or COMPLETED state (there could be 1 in cancelled and 1 in completed so simply all tasks in one of the states) - The task could be cancelled from any status starting from the OPEN - Service can be cancelled at any time and the tasks would be outo cancelled FURTHER REQUIREMENTS - Adjust the API for mobile and remove unnessesary endpoints. The main point is that the API for the mobile is mirrowing the Behaviour in web. ________________ Expected behaviour - cancellation logic remain intact - completion triggers the report creation - activity log remains the same - data validations from the tasks is removed - all views of the tasks adn services remain the same - old statuses are removed if not used - All validations inside of the taks remains DATA MIGRATION SERVICES OPENED --- CREATED TASKS OPENED --- CREATED BOOKED --- OPEN