A Task Completion Condition is a rule by which the Deepleex system automatically determines that a task is finished and moves it to the “Completed” status.
Completion conditions are used for automatic control of task closure without manual verification.
In the current version of the system (MVP), only one type of completion condition is supported.
What is it for
Completion conditions are used to:
Automatically close tasks
Dependent tasks
Eliminate the need for manual status checks
Ensure correct functioning of dependencies between tasks
This allows the system to automatically manage the state of tasks.
How it works
Linked task is completed
A task can be linked to another task (have a dependency or relation).
If the linked dependency task moves to the “Completed” status, the system automatically considers the current task completed as well.
This rule is applied to tasks that:
Depend on the completion of another task
Are logically tied to another task’s execution
Once the linked task is marked as completed, Deepleex automatically changes the status of the current task to “Completed”
Simplified logic
In simple terms:
A task is considered completed as soon as the task it depends on (or is related to) has been completed.
What we get as a result
Automatic task completion that happens without manually changing the status, while ensuring correct synchronization of related and dependent work.