# Adding a Ticket Custom Field

https://docs.wisecp.com/fr/adding-a-ticket-custom-field

Add translated and, when needed, required questions to the ticket form to collect complete structured information from clients in the right department.

## Reaching the Screen

From **Custom Fields**, choose **Add New Custom Field**: `{admin}/tickets/custom-fields/add`

Opening a field name from the list uses the same form in edit mode.

## What Is on the Screen

Language tabs keep field labels and option rows aligned. Structural choices such as department, type, requirement, status and order apply to every translation.

## Fields

- **Field Name**: Required in your primary language only. This is the question or label shown with the input.
- **Description**: Optional translated guidance shown with the field.
- **Department**: Limits the field to one department's tickets. None makes it available to all departments.
- **Field Type**: Text, Textarea, Number, Password, Select, Radio or Checkbox.
- **Options**: Required for Select, Radio and Checkbox. Each option needs a label in your primary language and can be dragged into order.
- **Required Field**: Prevents the client from opening the ticket without a value.
- **Active**: Inactive fields are not shown on ticket forms.
- **Sort Order**: Lower values place the field earlier. A new field with no order receives the next available position.
- **Existing Field**: Set automatically while editing.

## Tasks

### Create a text field

1. Enter the field name in your primary language. Open another language tab to translate it.
2. Choose the department and a text-oriented field type, then set Required, Active and Sort Order.
3. Create the field. It appears on matching new-ticket forms and ticket details.

### Create a choice field

1. Choose Select, Radio or Checkbox as the type.
2. Add each option, fill its label in your primary language and drag the rows into the intended order.
3. Save the field. Clients now choose from the same aligned option set in their own language.

## Things to Watch

> **Only the primary language is required**
> 
> In a language you leave blank, the client sees the field name and option labels from your primary language. This is what keeps option rows aligned across languages.

## Privileges

**Ticket Custom Fields** permission is required to add or edit a field.

## Related Screens

- [Ticket Custom Fields]({admin}/tickets/custom-fields)
- [Departments]({admin}/departments)