Custom fields
Every organization describes its estate in its own words: a cost centre, a data classification, a contract number, a criticality. Fields add them to the elements on its boards.
Define a field
Section titled “Define a field”Admins define fields in the organization’s settings. Every member sees them.
| Property | Notes |
|---|---|
| Key | Fixed once created: it is what stored values are filed under |
| Label | What people see. Can change |
| Type | text, choice, multi (several choices), date, number, url. Fixed once created |
| Choices | For choice and multi |
| Applies to | Which layers’ elements carry it |
| Order | Where it appears |
At most 50 fields per organization. Each change is recorded in the audit trail with its before and after.
The organization can also give its own list of values to a built-in field — compliance, for instance.
Values live on the elements
Section titled “Values live on the elements”A field’s values are stored on each element of each board. So:
- Removing a field rewrites no board. Values already entered stay on the elements.
- Changing a field’s choices changes what people can pick from, not what is already stored.
- A value is checked against the field’s type when saved, not against the organization’s current definition.
Owners
Section titled “Owners”Beside fields, every element can name its owner: a member or a team of the organization.