Task

A technical task decomposed from a Solution Item. Sequential completion of technical tasks will lead to implementing the corresponding solution item and project business tasks.

Tasks move to stages only if the following conditions are met:

• The task has defined competencies and estimates.
• The PI is defined.

User actions:

• Creating a technical task (title, description, estimated time for implementation, defining the necessary competency - skill, and level of mastery of that skill) at any time.
• Editing task data:
• Title and description - can be edited at any time.
• Required competency: 

✅ The technical task did not go through the DOING and REVIEW stages.

✅ The technical task is at the TO DO stage, and the assignee has not been appointed yet.

✅The technical task is at the DOING stage, or has already passed this stage - Сhanging the competence may lead to a change in the workflow - the task is moved to a new workflow.

Changing the performer: the performer is notified about being removed from the task.

Changing the stage: if the task is at the Doing stage, then when changing the competence, it is returned to the To Do stage.

❌ Changing the competence is impossible for a technical task at the REVIEW stage or if it has already passed the stages.

❌ Changing the competence is impossible for a technical task at the DONE stage.

• Time estimation for implementation:

✅ Time estimation can be done for technical tasks at the TO DO, DOING, and REVIEW stages.

❌ Changing the time estimation for implementation is impossible for a technical task at the DONE stage.

• Moving a task to another SI
• Manual assignment of performer
• Completion of work on a task at any stage of the workflow
• Creating/modifying dependencies between tasks can be done at any time.
• Deletion is possible if:

✅ Does not have any input/output dependencies.

✅ The task does not have an assigned executor

 Input/output dependencies between tasks:

A tech task can be linked to other tasks through input/output dependencies (sequence of execution) or be an autonomous element of decomposition of one Solution Item. When creating an incoming dependency, the system blocks the task.

In the Task card, where an incoming dependency is created, i.e., whose execution is only possible after the completion of work on the predecessor tech task, the symbol appears in the Blocked field, informing the user that the system is blocking the execution of this tech task for the performer. As soon as the predecessor tech task is completed (workflow DONE stage), i.e., passes all stages of the Workflow process from assigning the performer by the system to their execution and quality review by the reviewer, this tech task will be unblocked, and the symbol in the Blocked field, the user will be informed about it.