Individual work inside a project. This is the module where assignment is most obviously about workload rather than accountability.
A project task is the odd one out. A task is given to somebody rather than owned by them, so its owner is the Assigned to field rather than an Owner field. Rules set that instead; everything else behaves the same.
What you would route on
Any field on the module can be used, including ones you have added yourself. These are the ones businesses reach for:
| Field | Why you would route on it |
|---|---|
| Project | Keep a project’s tasks with its team. |
| Priority | Urgent work to whoever has capacity. |
| Due date | This week’s work to the people on shift. |
A worked example
A software team routes project tasks round-robin across the four developers, capped at six live tasks each. New work spreads automatically and nobody ends up with a queue of fourteen.
Caps and overflow
| Setting | Worth it here? |
|---|---|
| A cap per person | Yes — this is the clearest case for a cap in the whole product. |
| An overflow owner | Yes. |
Where to go next
- Writing the rule
- When it runs — on create, on edit, or both
- Capping how much each person gets
- Where the overflow goes
Something missing or wrong here? Tell us. A question that needed asking usually means a page that needed writing.