Project

General

Profile

Actions

roos-fs tasks #134

open

Create the proper linking between Service and the Tasks

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

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

0%

Estimated time:
18:00 h

Description

General
Use case, a service is a collection of tasks that are supposed to be attached to it. Tech service is created and tasks are assign to the service for all partisipants to see it.

Expected result

  • in the service the task could be attached to service
  • Multiple tasks could be attached to a service
  • Only task from the existing list of tasks could be added/attached
  • all tasks are visible in the list of tasks when the service is creted
    NOTE: the TASK in the task list is a TEMPLATE. THe task in the Service is a seperate entity that would withhold the infromation that would be provided from the technician.
    Why? since each task in the service would have its own unique date, technichian and status
Actions #1

Updated by Vadim Pariev 11 months ago

  • Assignee set to Alex Katasonov
Actions #2

Updated by Alex Katasonov 11 months ago

  • Status changed from Backlog to Open
Actions #3

Updated by Alex Katasonov 11 months ago

  • Status changed from Open to In progress
Actions #4

Updated by Alex Katasonov 11 months ago

  • Estimated time set to 15:00 h
Actions #5

Updated by Alex Katasonov 11 months ago

  • Estimated time changed from 15:00 h to 18:00 h
Actions #6

Updated by Alex Katasonov 10 months ago

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

Updated by Alex Katasonov 10 months ago

  • Status changed from In review to Deployed (QA)
Actions #8

Updated by Alex Katasonov 10 months ago

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

Updated by Albert Katasonov 5 days ago

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

Also available in: Atom PDF