What Is Mission Dependency?
Mission Dependency is a powerful control feature that ensures missions are completed in the correct order.
When dependency is enabled, a mission cannot be completed, tested, or moved forward until all required missions before it are finished. This guarantees that important steps are never skipped and work follows a structured process.
Why Mission Dependency Is Important
Mission Dependency helps organizations:
-
Prevent tasks from being completed prematurely
-
Enforce correct workflow order
-
Reduce human errors
-
Maintain quality standards
-
Ensure accountability at every stage
-
Improve delivery consistency across teams
This feature is especially useful for projects where one task depends on the completion of another.
Where Mission Dependency Works
Mission Dependency applies to:
-
Missions linked to projects
-
Missions inside the same workflow column
-
Movement between stages such as:
-
To Do
-
Queries
-
Testing
-
Done
-
It does not affect independent missions that are not part of a project (unless manually enabled).
How Mission Dependency Works
When Mission Dependency is enabled:
- Missions are ordered inside a project column
- Each mission must be completed in sequence
- Users cannot skip missions
- The system automatically checks task order
- Incomplete missions block progress
If a dependency rule is violated, the system prevents the action and displays a warning message.
Types of Mission Dependency
1️⃣ Project-Level Dependency
When enabled at the project level, all missions inside the project follow dependency rules.
Behavior:
-
Missions must be completed in order
-
Users cannot move a mission to Testing or Done unless previous missions are completed
-
Applies automatically to all new missions in the project
How to Enable:
-
Open Projects
-
Edit a project
-
Enable Mission Dependency
-
Save the project
2️⃣ Mission-Level Dependency
Mission dependency can also be controlled per mission.
Behavior:
-
Some missions can follow strict order
-
Other missions can be completed independently
-
Use Case:
-
Sequential tasks (Design → Development → Testing)
Parallel tasks (Multiple developers working at the same time)
Dependency With Sub-Missions
If a mission contains sub-missions (sub-tasks):
-
All sub-missions must be completed first
-
The parent mission cannot be marked as done until all sub-tasks are finished
-
Dependency validation checks sub-mission completion automatically
When You Should Use Mission Dependency
✔ Multi-step workflows
✔ Approval-based processes
✔ Development pipelines
✔ Quality-controlled projects
✔ Teams requiring strict order
Summary
Mission Dependency is a workflow protection system that ensures missions are completed in the right order, at the right time, by the right people.
By enforcing task sequence, it helps teams work smarter, avoid mistakes, and deliver projects with confidence and consistency.
