
Clone this issue
|
|
If you were logged in you would be able to see more operations.
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Allow the creation of tasks that are dependent on other tasks, where the subordinate tasks would be inactive until the first one was completed.
Example:
Ticket comes in that requires Network Provisioning, Hardware Delivery, and Billing.
Initial Support contact creates:
Task A) Provision Network
Task B) Deliver Hardware, but only after Task A is complete
Task C) Bill Client, but only after Task B is complete
|
|
Tasks and whole tickets, for larger jobs having dependant tickets would help separate the different conversations involved
|
|