## Application fields

Application fields are administrator-defined custom fields that extend issue forms and customer profiles. They work in a two-level architecture: first a field definition is created, then it is assigned to the desired module.

## Field definitions

Global field definitions are available under **Configuration → Application fields**. This is the central dictionary of all available fields in the system.

Each field has four configuration sections:

- **General** — field type, name (multilingual), description, unique field code, whether the field is editable by the user
- **Configuration** — settings specific to the field type (e.g. list values, constant value, visibility on the issue list, searchability)
- **Validations** — validation rules (required, unique, min/max length, regular expression, date range, etc.)
- **Display** — field width in the form layout

## Field types

| Type | Description |
|---|---|
| Text | Single-line text field |
| Long text | Multi-line text field |
| Email | Email address field |
| Number | Numeric field |
| List | Single value selection from a dropdown |
| Multi-list | Multiple value selection from a dropdown |
| Date | Date picker |
| Checkbox | Yes/no field |
| Radio | Single option selection (radio buttons) |
| File | File upload field |

## Assigning fields to modules

A field from the global definition can be assigned to one or more modules:

- **Issues** — fields on the issue details page (configured per issue type under **Configuration → Issue types → Fields**)
- **Customers** — fields on the customer profile
- **Remote forms** — fields on the public issue submission form
- **Status page** — fields visible on the public status page
- **Reports** — columns in reports

Each assignment allows overriding the name, description, configuration, and validations for that specific module. Field order is changed by dragging rows in the list.

---

## FAQ

### Can I change a field's type after it has been created?
No. The field type is fixed after saving. To change the type, delete the field and create a new one.

### Does deleting a field delete the data entered in that field in existing issues?
Yes. Deleting a field is irreversible — data saved in that field across all issues will be lost.

### Can the same field be assigned to multiple issue types?
Yes. A single field from the global definition can be assigned to multiple issue types, customers, and other modules simultaneously.

### How do I change the order of fields in a form?
Field order is changed by dragging rows in the field list for a given issue type or customer.

### What is the field code?
The code is a unique field identifier used in message templates, among other places. It may only contain lowercase letters, digits, and underscores. It cannot be changed after saving.

### Can a field have a constant value?
Yes. A field can have a constant value set — in that case it does not appear in forms and is filled in automatically.