Project settings
Overview
Three tabs: Project statuses, Milestone statuses and Project types.
One boundary up front, because it costs time in daily use: this holds only the project module's catalogues. Task statuses and task priorities are core master data and live under Task settings — they apply to tasks without a project too, after all.
Core tasks
Maintain project and milestone statuses. As everywhere in the system, statuses are data rather than program: they can be renamed, extended and reordered. The category preserves the meaning, so that a freely named status keeps counting correctly in reporting.
Maintain project types. The type is more than a label: every type supplies the billing defaults for new projects — the billing mode and whether work is billable by default.
This is the most consequential setting on the page. With the type set wrongly, every new project is created with the wrong default, and the mistake only surfaces at billing time — by which point the work has already been booked.
Recognise system types. Shipped types cannot be deleted. If one does not fit, create your own and leave the system type unused.
Fields in detail
The What it does column answers what changes in the system — not what the field is called. The grey name behind the label is the API field: the same thing runs under that name through automation, import and AI tools.
Project status and milestone status
Both carry the same fields.
| Field | Required | Values / format | What it does |
|---|---|---|---|
Key key | yes | short, stable text | The technical identifier for automation, reporting and the interface. Do not change it once projects sit on it. |
Label label | yes | text | What the user sees. Freely changeable without touching existing projects. |
Category category | no | open, active, done, cancelled | The business meaning behind your name. The system decides by it what counts as a running project and what enters utilisation — not by the name. |
Colour color | no | colour value | Colour of the status marker in list and timeline. |
Order sortOrder | no | number | Position in the selection. |
Default isDefault | no | yes/no | The status a new project or milestone starts on. |
Active active | no | yes/no | Off means no longer selectable; existing records keep it. |
Project type
| Field | Required | Values / format | What it does |
|---|---|---|---|
Key key | yes | text, max. 50 characters | Technical identifier; do not change once projects sit on it. |
Label label | yes | text, max. 100 characters | What the user sees. |
Billing mode billingMode | no | by time, by milestone, against quota | What a new project of this type is pre-filled with. The real decision is made on the project — this only says what is usual. |
Billable by default defaultBillable | no | yes/no | What time entries in projects of this type are pre-filled with. |
Colour color | no | colour value | Colour of the type in lists. |
Order sortOrder | no | number | Position in the selection. |
Default isDefault | no | yes/no | The type a new project starts as. |
Active active | no | yes/no | Off means no longer selectable. |
Settings & permissions
- Module
module.projects. - Permission
projects.config.manage. - A status's key is permanent, the label changeable at any time.
- Deactivate rather than delete: a deactivated status is no longer offered but stays readable on
existing projects.
- Templates build on this — see Project templates.
FAQ & troubleshooting
Task statuses are missing here. Correct — they live under Task settings, because they apply outside projects as well.
New projects are wrongly not billable. Check the project type: it supplies the default. It can be overridden on the individual project.
A system type cannot be deleted. By design. Create your own type.
A status counts wrongly in reporting. Check its category — without it the system does not know whether it means open or finished.