Task settings
Overview
This is where the master data around tasks is maintained: the global task lists plus statuses and priorities. The page is organised into three tabs — Task lists, Task statuses and Task priorities.
Project-specific lists do not belong here. They are managed inside the respective project. Only the lists that apply across projects are global.
Statuses and priorities are deliberately data rather than fixed program code. That is why you can rename, reorder and extend them without anybody having to ship a release.
Core tasks
Maintain global lists. The first tab manages the task lists that are available everywhere.
Adjust statuses. Every status carries a key, a label, a category, a colour, a sort order and the markers Default and Active.
The category is the field most often overlooked and the one with the greatest consequences: it maps a freely named status onto one of four meanings — Open, Active, Done, Cancelled. That is how the system knows whether a task is open. A status called "With the customer" without a category counts correctly in no evaluation.
Adjust priorities. Priorities additionally carry a weight. It determines the ranking in sorting — not the position in this list.
Set the default. The entry marked Default is pre-selected on new tasks.
Fields in detail
Three tabs, three masks: the task list, the task status and the task priority.
Task list
| Field | Required | Values / format | What it does |
|---|---|---|---|
Name name | yes | text, max. 255 characters | What the list is called. It appears as a column on the board and as a choice on the task. |
Colour color | no | colour value, max. 7 characters (#RRGGBB) | Colour of the column. |
Visible to customers customerVisible | no | yes/no (defaults to no) | Whether the list appears in the customer portal. The switch can also be flipped straight in the row. |
Visible to externals externalVisible | no | yes/no (defaults to no) | Whether external contributors — freelancers, partners — see the list. It applies to the list, not to its tasks: what an external sees in terms of tasks is decided solely by their project cut. |
Description description | no | text, max. 500 characters | What the list is meant for. |
Planned effort (minutes) estimateMinutes | no | number, 0 or greater | The effort planned for the whole list. A container, not a sum: the tasks in the list consume this value, they do not add up to it. That shows how much of the plan is still free. Empty = no plan. |
Order sortOrder | no | number | Position on the board — left to right, the path a task takes. Set by dragging the row, not in the dialog. |
Archived archived | no | yes/no | Takes the list out of day-to-day operation without deleting it. Through archive or restore in the row. |
Project projectId | no | an existing project | Which project the list belongs to. Always empty on this page — only global lists are created here; project lists are maintained in the project. |
Brand brandId | no | one of your brands | Limits the list to one brand. Not offered in the mask; interface and automation only. |
Deleting removes only the list — the assigned tasks remain, then without a list.
Task status
| Field | Required | Values / format | What it does |
|---|---|---|---|
Key key | yes | short text without spaces | The permanent identity of the status. It is attached to existing tasks and cannot be renamed afterwards — only the label can. |
Label label | yes | text | How the status appears in lists, board and filters. Changeable at any time. |
Category category | yes | open · active · done · cancelled | The field with the greatest consequences. It maps a freely named status to one of the four meanings; that is how the system knows whether a task is open. A status "with the customer" in the wrong category counts wrongly in every report. |
Colour color | no | colour value | Colour of the status tag. |
Follow-up status on timer start timerStartStatusKey | no | key of another active status, max. 50 characters | If someone starts a stopwatch on a task in this status, the task moves to the chosen status. Empty = no change. An unknown key or a reference to itself is rejected. |
Order sortOrder | no | number | Position in the selection and on the board. |
Default isDefault | no | yes/no | What a new task is pre-filled with. |
Active active | no | yes/no | Off takes the status out of the selection; existing tasks keep it. Deactivate instead of deleting — deleting leaves tasks without a valid status. |
Task priority
| Field | Required | Values / format | What it does |
|---|---|---|---|
Key key | yes | short text without spaces | The permanent identity; as with the status, not renameable. |
Label label | yes | text | How the priority appears. |
Colour color | no | colour value | Colour of the priority tag. |
Weight weight | no | number, higher = more urgent | The rank in sorting. It is not the same as the order: sorting follows the weight, the selection follows the order. |
Order sortOrder | no | number | Position in the selection list. |
Default isDefault | no | yes/no | What a new task is pre-filled with. |
Active active | no | yes/no | Off takes the priority out of the selection. |
A list is not a status. It structures the work, the status describes its state. Mixing the two — a list "done" next to a status "done" — reliably leads to board and reports claiming different things.
Settings & permissions
- No route permission of its own. The page is reachable; changing is checked by the server —
task lists through workitem.list.manage, statuses and priorities through workitem.config.manage.
- The key is permanent. It is attached to tasks already captured. The label you may change at
any time — it is the display, the key is the identity.
- Deactivate rather than delete. A deactivated status is no longer offered but stays on existing
tasks.
- Applies everywhere. What is set here holds in lists, filters,
automations and reporting alike.
FAQ & troubleshooting
A custom status counts wrongly in reports. Check the category. Without the right mapping the system does not know whether the status means open or finished.
Priorities do not sort as expected. Sorting follows the weight, not the order in this list.
A project list is missing here. Correct — project-specific lists are maintained in the project, not here.
A deleted status orphaned some tasks. Which is why you deactivate rather than delete. Move the affected tasks to a valid status.