*** How custom fields work Custom fields are tied to specific forms. When someone creates a ticket using a form, they see both standard system fields (like title and description) plus any custom fields configured for that form. **Example:** A “Bug Report” form might include custom fields for bug severity, browser type, and steps to reproduce. A “Feature Request” form might include custom fields for business justification, priority level, and target users. Custom fields are only available when creating tickets through forms. *** Field types Single-line text input for short responses like names, titles, or brief descriptions. Multi-line text input for longer descriptions, explanations, or detailed information. Numeric input with validation for quantities, counts, or measurements. Date picker for scheduling, deadlines, or date-related information. When used in a [title template](/documentation/tickets/forms/overview#title-templates), date fields support format suffixes to control how the date displays in the generated title. Time input for selecting specific times of day. Time duration input for tracking time spans or estimated completion times. Select from predefined timezone options for scheduling and time-related information. Yes/No checkbox for binary choices or confirmations. Single-choice dropdown menu from predefined options. Multiple-choice dropdown menu allowing selection of multiple options. Choose a single organization member for assignments or mentions. Choose multiple organization members for assignments or mentions. Select from user groups in your organization. * Configure an **allowlist** with no item limit to restrict which groups appear as options * Filter by **source** to show only groups from a specific provider (Okta, Google Workspace, or groups created in Ravenna) * Manually created groups only appear in their assigned workspace. Synced groups are visible across all workspaces. Select from available tags to categorize tickets. Select from applications connected to your organization. Select multiple applications connected to your organization. * Configure an **allowlist** with no item limit to restrict which applications appear as options Select from application groups in your organization. Select from predefined ticket type options (e.g., Service, Incident, Question). Select from defined access levels for permission management. Upload files and attachments to tickets. Configure allowed file types and size limits. *** Create custom fields Create custom fields centrally in workspace settings: Go to **Settings > Fields** in your workspace. Click **Create Custom Field**. Fill in the required information: * **Label**: The name that appears on the form * **Description**: Help text explaining what this field is for * **Type**: Choose from available field types * **Required**: Toggle whether this field must be filled out. Turning this on at the workspace level makes the field required everywhere it appears and locks the per-form **Required** toggle so individual forms cannot opt out. Click **Create** to save your custom field. Create and manage custom fields directly within forms: Go to **Settings > Forms**. Select an existing form or create a new one. Drag and drop fields from the right panel into your form. The right panel has three tabs: * **Custom**: Create new custom fields * **Existing**: Use existing custom fields from other forms * **System**: Add system fields Use the dropdown menu in each custom field item to edit field properties. Toggle the private option to make a custom field visible only for the current form. *** Use existing fields Existing custom fields are non-private fields created from other forms or settings. Find them in the **Existing Custom Fields** tab in the form builder. These fields are shared across forms, meaning you can reuse them without recreating them. When you update an existing custom field that’s shared across multiple forms, the changes apply to all forms using that field. *** Per-form label and description overrides Override the **label** and **description** of a shared custom field on a single form without affecting how the field appears on other forms. Use overrides when the same underlying data point needs different wording per audience. **Example:** A shared **Department** field can show as “Your department” on an employee-facing onboarding form and “Requesting department” on an internal procurement form, while still writing to the same field on every ticket. **Configure an override:** Go to **Settings > Forms** and select the form. In the form builder, click the field’s title to rename it inline, or open the field’s menu and choose **Edit** to update the description. Changes save automatically. The override applies only to this form. Clear an override to fall back to the field’s shared label or description. Overrides do not change the field’s key, type, options, or validation — only the displayed text on this form. Custom fields cannot be deleted when they are being used in a form. Preview impacted forms When you edit a shared custom field, Ravenna asks you to confirm the change and lists every form the field is attached to. When you try to delete a shared field that’s still in use, the error dialog shows the same list so you can see exactly where it’s referenced. Each entry in the list links directly to the affected form. The form you’re currently editing is labeled **Current** and is not clickable. Use this list to: * Review which forms will be affected before saving a label, description, or option change. * Jump to other forms that need follow-up edits. * Locate every form that still references a field you want to delete. *** Use custom fields Once you’ve created custom fields and assigned them to forms: **Ticket creation** * Users see custom fields when creating tickets with that form **Ticket display** * Custom field values appear in ticket details * In table views, custom field columns are hidden by default. Show them from the column visibility menu. * URLs in text and textarea fields are automatically converted to clickable links, including `https://`, `http://`, `www.`, and bare domain formats **Ticket updates** * Custom field values can be updated after ticket creation from the ticket details page Learn more about [setting up forms](/documentation/tickets/forms/overview) and assigning custom fields to create complete ticket templates