Shape the task workflow: stages, work status and roles
What this does
The task workflow of a WindoorERP project has two layers. The stage — the kanban column — is shared by the team and configurable; the Work Status flag stamped by the header buttons is a fixed four-step ladder. This article covers what each is for, where the stage lists are maintained, and what roles and tags add. It documents what ships: automated activity plans and project-level stages are not part of this build's menus.
Before you start
- Fleet-wide stage editing lives under Installation › Configuration › Task Stages — that screen lists every task stage in the database, technical projects' included.
- Renaming a stage there renames it for every project that shares it.
Set up the workflow
-
01
Leave the seeded ladder alone unless you truly need another shape — every typed project starts with New › In Progress › QA › Done and a folded Cancelled, so all boards read the same.
-
02
To add a column for one project only, use the board itself: open the project's tasks and add a stage at the end of the columns.
-
03
To change the shared ladder, open Installation › Configuration › Task Stages: name, sequence and the Folded in Kanban flag per stage.
-
04
Keep terminal stages folded — folding is what marks a task closed for the project's completion percentage.
-
05
Maintain Project Tags in the same Configuration menu for cross-project labels (villa, tower, government…).
Stage versus Work Status
| Layer | Nature | Who changes it |
|---|---|---|
| Stage | Configurable columns, owned by the project; folded stages count as closed. | Anyone working the board — drag the card or click the stage bar. |
| Work Status | Fixed flag: Draft, In Progress, QA, Done. Tracked in the chatter. | The four header buttons on the task. They set the flag only — the card does not move by itself. |
| Personal Stage | A private column per user, invisible to others. | Each assignee, for their own ordering. |
Because the two shared layers move independently, agree with the team which one is authoritative for "done" — most teams pick the stage, and use Work Status as an audit stamp of who declared what, when.
Roles
Tasks carry a Roles field — labels such as who surveys, who checks, who installs on this task. Roles are assignment vocabulary, not permissions: they grant nothing and hide nothing. Use them when one task involves several people in different capacities and the assignee list alone loses that information.
Troubleshooting
A stage renamed for one project changed everywhere — the stage record was shared; give the project its own stage from its board instead of renaming the common one.
The completion percentage ignores finished tasks — their stage is not folded; fold the terminal stage.
You are looking for Project Stages, Activity Plans or a Project configuration menu from standard Odoo — they are not part of WindoorERP's menu set; the task-stage screen above and the per-project Settings tab are the supported configuration surfaces.
Common mistakes
- Deleting a stage that still holds tasks instead of folding or renaming it.
- Building a different stage ladder per project without need — identical boards are what make cross-project supervision readable.
Was this article helpful?
Thanks — your feedback helps.
Running a window or door factory?
Ask for a demo