Project

General

Profile

Actions

roos-fs tasks #131

open

Extend the API for Service creation / task creation (for Mobile users)

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

Status:
Closed
Priority:
Normal
Assignee:
Farzam Azhar
Start date:
06/20/2025
Due date:
% Done:

0%

Estimated time:
12:00 h

Description

General
Use case - there are some open contracts that dictate that some services may be made without any preliminary appointmnet booking - that means that the car enters the Workshop and it is requested to perform to change telematic device (real case) and the technician at the location ened to perform following steps: find the car using the VIN/LP number. As soon as found the user needs to create a service for this car, be able to assign the task from the list. And then take care about this task.

Expeted result

  • Mobile app user is able to enter all the fields in the service creation mask analog to the web app part
  • the service creation include also the selection of the tasks templates from the list (that is fetched from the DB)
  • Ensure API responses are optimized for mobile use (lightweight payloads)
  • The API is secure and API could be called only by the authorised user (Requires valid access token)
  • the API documentation is provided in the https://redmine.matecube-internal.ddns.net/projects/roos-fs/wiki part
  • The user can add the task to already created service
  • User can fill out the check lists attached to the Task
  • User is able to see this data at any time
    NOTE
  • the tasks could be created only within the existing service or attached to newly created service
  • mobile user CAN NOT create a task TEMPLATE
  • mobile user CAN only edit the description to the task but not the FIELDS
Actions #1

Updated by Vadim Pariev 11 months ago

  • Assignee set to Alex Katasonov
Actions #2

Updated by Vadim Pariev 10 months ago

  • Subject changed from create API for Service creation (for Mobile users) to Extend the API for Service creation / task creation (for Mobile users)
  • Description updated (diff)
  • Assignee changed from Alex Katasonov to Farzam Azhar
Actions #3

Updated by Vadim Pariev 10 months ago

  • Status changed from Backlog to Open
Actions #4

Updated by Farzam Azhar 10 months ago

  • Status changed from Open to In progress
Actions #5

Updated by Farzam Azhar 10 months ago · Edited

  • Estimated time set to 12:00 h

@Vadim Pariev I have the following questions for this ticket. Please clarify when convenient for you.

  • The tasks could be created only within the existing service or attached to a newly created service

    • While creating a new service, the user can only add existing tasks, not create new ones.
    • On an existing service, the user can create a new task by selecting from task templates. Is this understanding correct?
  • Mobile user CAN only edit the description of the task, but not the FIELDS

    • When creating a new task from a task template, can the user fill out all fields (based on the web App)?
    • But when editing an existing task, the user can only update the description, not any of the other fields?
  • The user can add the task to an already created task

    • Should this say: "User can add a task to an already created service"?
  • The user can fill out the checklists attached to the Task

    • And the mobile user should be able to view and fill out the checklist fields as part of completing the task?
Actions #6

Updated by Vadim Pariev 10 months ago

  • Description updated (diff)
Actions #7

Updated by Vadim Pariev 10 months ago · Edited

the user can ONLY add a task from the templates - yes
wheт adding the task the user is able only to edit description
yes
yes

Actions #8

Updated by Farzam Azhar 10 months ago

  • Status changed from In progress to In review
Actions #9

Updated by Alex Katasonov 10 months ago

  • Status changed from In review to Open
Actions #10

Updated by Farzam Azhar 10 months ago

  • Status changed from Open to In progress
Actions #11

Updated by Farzam Azhar 10 months ago

  • Status changed from In progress to Open
Actions #12

Updated by Alex Katasonov 10 months ago

  • Status changed from Open to Deployed (QA)
Actions #14

Updated by Vadim Pariev 10 months ago

  • Status changed from Deployed (QA) to Closed
Actions #15

Updated by Albert Katasonov 5 days ago

  • Project changed from 8 to Roos-fs-ZIP
Actions

Also available in: Atom PDF