Articles in this section
Category / Section

How to Add a New Custom Field to a Ticket Form

5 mins read
Updated:

To add a new custom field to a ticket form, follow the given steps:

  1. Go to the Ticket Fields module.
  2. Click the Add Ticket Field button on the rights.

Adding_a_Ticket_Field.png

Check out this video tutorial for more details.

Field configurations when creating a new custom field

Consider the following field configurations when creating a new custom field:

  • Field Type – You can create a custom ticket field using the following custom field types.
  • Textbox (single line)
  • Textbox (multi-line)
  • Checkbox
  • Yes or No
  • Date
  • Date Time
  • Numeric
  • Decimal
  • Dropdown (single-select)
  • Dropdown (multi-select)
  • Regex
  • URL
  • Lookup
  • Label for Agent Portal – Displays the filed name in the create ticket form and ticket properties of the agent portal.
  • Label for Customer Portal – Displays the field name in the create ticket form and ticket properties of the customer portal.
  • API Name – You can specify an API name for the custom field. Using this name, you can fetch or update the corresponding field data via Rest APIs.
  • Note Message – Specifies a help information text for the field
  • Note Message Display – Allows you to choose where to display the note message, either below the field or as an info icon near the field.
  • Below field – Displays the note message below the created field.
  • As an Info icon near the field – An info icon is placed near the field. When you hover over the info icon, the note message appears as a tooltip.

Field_configuration.png

Field display condition

By using the field display condition, you can choose a field to display only when the specified conditions have been met. To learn how to configure field display conditions, please refer to this article.

Field configurations in the agent portal

Field configurations in the agent portal specify the field visibility and mandatory status for the custom field. They include:

  • Agent can edit - Controls the field’s visibility. If it’s unchecked, the custom field will only appear as a read-only field on the ticket detail properties.
  • Visible while creating ticket - Controls the field’s visibility. If it’s checked the custom field will appear on the ticket creation form at the time of ticket creation.
  • Agents can edit the value after submitting the ticket - Allows the agents to edit the field after ticket creation.
  • Mandatory field - You can set a field to be mandatory when creating or updating tickets.
  • Mandatory field based on status change - You can set a field to be mandatory either for any status change or while closing/solving tickets.

Agent_portal_field_configuration_settings.png

  • When the Agent can edit box is unchecked, the Country field on the ticket properties is displayed as read-only.

Configuration_for_read-only.png

Field configurations in the customer portal

The field configurations for the customer portal can be set in a similar manner as the agent portal:

  • Visible to user - If this option is unchecked, the custom field will not be visible in the customer portal.
  • User can edit - If this option is unchecked, the custom field in the customer portal will only appear as a read-only field in the ticket detail properties.
  • Visible while creating ticket- Controls the field’s visibility. If it’s checked the custom field will appear on the ticket creation form at the time of ticket creation in the customer portal.
  • User can edit the value after submitting the ticket - Allows the user to edit the field after ticket creation.
  • Mandatory status- You can set the field status as mandatory by checking or unchecking the mandatory option.
  • If the Agent can edit box is unchecked, you cannot make a custom field mandatory.
  • If the User can edit box is unchecked, you cannot make a custom field mandatory.

Field_Configuration_in_CP.png

Dropdown option value

The option values for the dropdown type custom field can be added as strings. If there are multiple values, use a comma to separate them to add.
You can perform the following actions to the dropdown option values:

  • Renaming- Updates the value across all existing tickets where it has been used.
  • Deleting- Removed the value from all existing tickets where it was used, leaving the associated field empty. After an option value is deleted, it cannot be restored.

Instead of deleting or renaming the option values, you can mark old option values as read-only by enabling the Read-Only checkbox. This will make the value not appear in dropdown list restricting it from being selected in future tickets while keeping it visible in existing ones.

Pease refer to this article for more information on how to manage dropdown values.

  • Dragging and dropping- Option values can be dragged and dropped for sorting. You can also sort them in alphabetic order.
  • Setting a default value- The default value is filled automatically when a form is loaded in the agent or customer portal.

dropdown_1.png

Dropdown_2.png

  • The field created will not be automatically added to a ticket form.
  • You can map the created field to a respective brand form using the ticket forms module.
  • After creating a ticket field, you can edit the field name, but the type of the field cannot be changed, for additional information, please refer to this article.
  • You can also configure field dependency for the dropdown or multi-select fields. Please refer to this article to learn how to set up field dependency.

Managing Sections in a Ticket Form

Adding a New Section

To add a new section to a ticket form:

  1. Open the ticket form you want to configure.
  2. Click the Add Section button.
  3. Provide the section name.
  4. (Optional) To make this section the default for adding fields, check the Set as default checkbox.
  5. Click the Create button to add the new section.

Adding_a_section.gif

  • The System section is used to manage system fields, so it cannot be deleted or reordered. It always remains fixed at the top of the form.
  • The default section serves as a fallback destination for fields when no other section is selected during creation and therefore cannot be deleted.

Renaming, Reordering, Deleting and Setting a Section as Default

  1. Renaming a section
  • To rename the section, select Edit Section from the menu options.
  • Modify the section name, then click Update to save the changes.

Renaming_a_section.gif

  1. Reordering a section

To reorder sections, either:

  • Select Reorder Section from the context menu, or
  • Click the Reorder button at the top of the grid.

Reordering options.png

  • Drag and drop the sections into the desired order, then click Update to save the changes.

Reordering_a_section.gif

  1. Setting a section as default

To set a section as the default, select Set as default from the context menu.

Setting a section as default.png

  1. Deleting a Section

To delete a section:

  • Open the context menu of the section you want to delete.
  • Select Delete from the menu options.
  • Choose one of the three available options to manage the fields associated with the section.
  • Click the Delete button to confirm and complete the deletion.

Deleting_a_section.gif

Adding custom fields to a ticket form

Adding fields to ticket forms can be accomplished in two ways, namely.

  • Adding a new field.
  • Adding the existing fields from the ticket fields module.

Adding existing fields

To add an existing field, follow the given steps:

  1. Open the ticket form you want to configure.
  2. Click the Add Field button to the right of the section where you want to add a field.
  3. A side bar will appear with the list of all the existing ticket fields. Select multiple fields to be added to the form and click Add.

Adding_existing_fields.gif

The fields will be added to the selected form.

Adding new fields

To add a new field, follow the given steps:

  1. Open the ticket form you want to configure.
  2. Click the Add Field button to the right of the section where you want to add a field.
  3. A sidebar will appear, displaying a list of all existing ticket fields. Click the Add New Field button in the top-right corner of the sidebar.
  4. This will open a new sidebar for adding a new custom field. Complete the required configuration, then click the Add button.

Adding_new_fields.gif

The newly added ticket field will also appear in the Ticket Fields module.

The field you created—for example, “Country”—will appear in the Create Ticket form under the section where it was added.

New field.png

Reordering fields

Follow the given steps below to reorder fields in the ticket form:

  1. Open the ticket form you want to configure.
  2. Drag and drop a field to your desired position in the form. It will be updated automatically.

Reordering field.png

Subject field reorderd.png

The Brand field is fixed and can’t be reordered.

Moving fields to another section

To move a field to a different section in the ticket form, the following methods can be used:

  1. Drag and drop the field into the desired section. The change will be saved automatically.

Drag_and_drop_field_to_other_section.gif

  1. Use the context menu
  • Click the field’s context menu and select Move to Another Section from the menu options.

  • In the dialog box that appears, choose the target section from the dropdown.

  • Click on the Move button to apply the changes.

Move_a_field_to_another_section.gif

System fields, except for Type and External Reference ID, cannot be moved to other sections. They will always remain in the System section.

Permission for adding a new custom field

To add a new custom field or configure ticket forms, an agent must have the Manage fields and forms permission assigned to their role.
Please refer to this article to learn more about Roles and Permissions.

Roles and permissions.png

Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
Comments (0)
Please  to leave a comment
Access denied
Access denied