WORKFLOW - The process that a task goes through from creation to successful completion. The Workflow system is visually represented by a sequence of production stages aimed at coordinating, controlling, and managing the quality of task implementation flows in a project.
Workflow has a strictly defined structure consisting of primary stages (Workflow Stages)—TO DO, DOING, DONE. Workflow Stages determine and control the progress of project task execution.
The system allows users to customize the QUALITY MANAGEMENT PROCESS stage (on the WORKFLOW screen). Customization refers to users creating individual stages within the QMP stage based on internal company policy rules or the need to incorporate additional quality control actions for implemented tasks and project objectives.
A user can assign one workflow to a skill.
Rules for the relationship between a skill and its workflow:
- When creating a root skill, the system automatically creates a workflow with default stages: TO DO, DOING, DONE (all workflows are displayed on the Kanban board). So, suppose all the tasks assigned to this skill in the future do not require quality management stages (Quality Management Process) and will be considered completed (DONE) as soon as the executor finishes working on them. In that case, the user does not need to create a workflow. It will be created automatically.
Default workflow - automatically created by the system. It is displayed on the KANBAN screen. The user cannot change the process structure or edit its data.
Custom workflow—manually created by the user. It is displayed on both WORKFLOW and KANBAN screens. The user can change the process structure by adding custom stages to the QUALITY MANAGEMENT PROCESS and editing its data on the WORKFLOW screen.
- The system assigns the root skill's workflow (Parent workflow) to all child skills. If required by project tasks and goals, the user can modify the default workflow of a child skill in the SKILL WORKFLOW sidebar by creating a new one or selecting from existing workflows (Custom workflow).
User actions:
- Create new workflow—creating a workflow. The user must perform this action if the tasks assigned to this skill in the future require quality management stage(s) (Quality Management Process). Creating and editing additional QMP stages takes place on the WORKFLOW screen.
- Select workflow - choosing from existing workflows created by the user manually.
- Replacing workflow for a skill:
✅The skill does not have any subskills - allowed.
✅The skill already has subskills:
- those that inherited the workflow from the parent skill - allowed
- if a subskill has a different workflow than the parent, the replacement does not occur.
When there are tasks in the workflow stages:
✅TO DO, DOING - allowed. Tasks move to the new workflow.
❌QUALITY MANAGEMENT PROCESS - not allowed
✅DONE - allowed. Tasks remain in the workflow in which they were completed.
-
Breaking the link between a skill and a workflow:
Deleting a skill leads to breaking connections between the skill and the workflow.
When deleting a Skill workflow created by the user to customize the QUALITY MANAGEMENT PROCESS stage (on the WORKFLOW screen), it is not automatically deleted.
When deleting a system-created Skill workflow on the Kanban screen, it automatically gets removed according to the following rules:
✅ If there are no tasks on the workflow stages - deletion is allowed.
If there are tasks in the workflow stages:
✅ For stages TO DO and DOING - Deletion is allowed. Tasks will transition to a new workflow.
❌ For QUALITY MANAGEMENT PROCESS - Deletion is not allowed.
❌ For DONE - Deletion is not allowed since the workflow is displayed on the Kanban screen.
This workflow is selected as a custom process for the Pipeline stage, requiring user confirmation for workflow deletion. Upon receiving additional confirmation, the link will be severed, and the workflow will be deleted.
Comments
0 comments
Please sign in to leave a comment.