Project (Example)
To better understand how task management works in the system, let's walk through a real-world example.
The Scenario:
Consider a company called ShopSwift — an ecommerce business that manages the entire order lifecycle in-house, from receiving customer orders, picking up products directly from sellers, to delivering them without any third-party involvement.
In the system, ShopSwift is set up as follows:
- Project Name: ShopSwift
- Project Category: Ecommerce
- Platforms: Admin Panel, Customer Panel, Warehouse Management Panel, Shipment Panel
The company is building its ecommerce website. For the Customer Panel platform, the following modules have been identified:
- My Profile
- Cart Management
- Favorites
- Order History & Data Management
The Task Flow:
The task flow for this project has been designed to mirror the real-world development lifecycle:
| Stage | What It Means |
|---|---|
| Unassigned | Task has only a title — no module or platform added yet |
| Open | Planning phase — requirements are being gathered and discussed |
| Active | Development phase — the feature is being built |
| On Hold | Work is paused due to a dependency or blocker |
| QA | Testing phase — the feature is being tested by QA |
| Complete | Development and QA cycle is done — pending go-live |
| Live | Feature is live and being used by customers |
Example: Creating and Moving a Task
Let's say the project manager wants to track the work for the Cart Management module on the Customer Panel platform. They create a task titled "Implement Add to Cart Functionality".
Step 1 — Task Created (Unassigned)
The task is created with only a title at this point. Since no module or platform has been assigned yet, it lands in the Unassigned stage automatically.
Step 2 — Details Added (Open)
The project manager assigns the module as Cart Management and the platform as Customer Panel. The task now moves to the Open stage, indicating it is in the planning phase. The start date, due date, estimation, priority, and assignee are also filled in at this point.
Step 3 — Development Begins (Active)
Once planning is complete and the developer starts working on the feature, the task is moved to the Active stage, indicating active development is underway.
Step 4 — Blocked Temporarily (On Hold)
During development, the team realizes they are waiting for the payment gateway API credentials from the client. The task is moved to On Hold until the blocker is resolved.
Step 5 — Testing Phase (QA)
Once development is complete, the task is moved to the QA stage. The QA engineer tests the cart functionality against the defined test cases. If any issues are found, an issue is raised and the task may cycle back to Active for the fix before returning to QA.
Step 6 — Development & QA Complete (Complete)
Once QA has signed off on the feature, the task moves to the Complete stage. This means the feature is fully built and tested but is pending deployment to the live environment.
Step 7 — Feature Goes Live (Live)
After the client approves the deployment, the task is moved to the Live stage, confirming that the Add to Cart functionality is now available to end users on the ShopSwift platform.
This flow ensures full visibility into every task's progress — from the moment it is created to the moment it reaches the hands of the customer.