Introduction
This reference explains all available options when creating or editing a custom field in Administration > Custom fields.
Target Audience
- Administrator
Definition of Custom Field Options
| Name | Description |
|---|---|
| Format | Select the format of the custom field (e.g., Text, Number, Date, etc.). |
| Name | The name of the custom field. Required field. |
| Group | Categorization of the field into a group. Optional. |
| Description | Text description to explain the purpose of the field. |
| Min - Max length | Define minimum and maximum allowed text length (for text fields). |
| Default value | Set a value that will be pre-filled by default. |
| Link values to URL | Make the entered values clickable as links if URLs are provided. |
| Visible | Choose who can see the custom field: any user or specific roles only. |
| Visible for helpdesk users | Make the field visible for helpdesk users. |
| Editable for helpdesk users | Allow helpdesk users to edit the field. |
| Trackers | Select for which trackers (task types) the custom field should be available. |
| Projects | Select for which projects the custom field should be available. |
| Project Templates | Select for which project templates the custom field should be available. |
| Special visibility | Enable additional, special visibility settings for more complex needs. |
| Required | Make the field mandatory to fill in. |
| For all projects | Automatically apply the field to all projects. |
| Used as a filter | Allow the field to be used as a filter in lists and reports. |
| Searchable | Allow the field’s content to be searchable. |
| Show as additional attribute | Display the field as an extra attribute in selected views. |
| Email notifications | Include the field in email notifications. |
| Do not export | Prevent this field’s value from being exported in data exports. |
Usage Notes
- Fields marked with * are required for the field to be created.
- Format selection determines what additional settings appear.
- Special visibility is useful for complex roles and permission control cases.
Notice
When using "Do not export", make sure users are informed, as the data will not appear in exported files even if visible in the system.
Examples
- Creating a custom field "Customer Priority" visible only to Project Managers.
- Adding a URL-linked custom field for external documentation references.
