The Ticket Field Manager app allows an administrator to quickly hide, require, and disable certain ticket fields and drop-down options in the Zendesk Support agent interface.
This article contains the following topics:
Related articles:
Installation
The Ticket Field manager is installed from the Zendesk Marketplace.
To install the app
- In Zendesk Support, click Admin (
), then select Apps > Marketplace. Enter "Ticket Field Manager" in the search bar at the upper right of the page.
- Double-click on the Ticket Field Manager app icon, and click Install.
- In the Installation section, enter a name for the Ticket Field Manager app, and enable group and role restrictions if required. These configuration options are also available after installation by navigating to Admin > Apps > Manage.
- On the app details page, click Install.
Configuring the app
Once the app is installed, you can go into Admin > Apps > Manage, click the gear icon on the Ticket Field Manager app, and select Change settings.
In the settings, you can configure the ticket field behavior by updating the provided fields and adding a comma separated list of fields. For a custom ticket fields, use the field ID except when specifying hidden dropdown field options which uses the format full `custom_field_` and ID.
Note: The list of fields must have a space after each comma.
-
Required form fields: Ticket fields that are required when creating or updating a ticket. For example:
field1, field2, field3, 360015591993
-
Read-only form fields: Ticket fields that are shown to the user but are not editable. For example:
field1, field2, field3, 360015591993
- Allowed groups for read-only form fields: This is a list of IDs of groups that should not have the read-only restrictions applied.
-
Hidden form fields: Ticket fields that should be hidden from the agent when creating or updating a ticket. For example:
field1, field2, field3, 360015591993
- Allowed groups for hidden form fields: This is a list of IDs of groups that should not have the hidden field restrictions applied.
- Allowed groups for hidden dropdown options: A comma separated list of group IDs that do not have any hidden options in dropdowns applied.
-
Hide dropdown form options: Hide options for a given dropdown field. The format is [{"name": "type", "value": "problem"}], or for custom fields [{"name": "custom_field_3600152073", "value": "brushed_silver"}]. Note: When setting the value, you need to use the tag of the pull down option. When editing the pull down options in the ticket field if you click on "Show tags", you will see the tag value that will need to be used.
Also, this feature only works for hiding options from dropdown field types and is not available for multi-select field types.
To hide multiple dropdown values including those in the same field, use the format as shown in the following example.
[{"name": "type", "value": "problem"},
{"name": "custom_field_360015592073", "value": "diamond"},
{"name": "custom_field_360015592073", "value": "nickel_plated"},
{"name": "assignee", "value": "387300360473"}]
Notice that the name must be listed with the name and value for each option to be hidden, even for options in the same dropdown field.
Available ticket fields
Some available ticket fields include the following:
- requester
- assignee
- collaborator
- sharedWith
- status
- ticket_form_id (the ticket form dropdown)
- tags
- type
- priority
- problem
- custom field
For a complete listing of available fields for use in the form settings, see Zendesk Support placeholders reference.
Using the app
After creating a ticket or opening an existing ticket, you will see that the fields are now required based on the list defined in Required Form Fields. In this example, this includes Assignee, Tags, Type, and Priority.
If option in dropdown fields were hidden, you'll see that those options no longer appear for those roles and groups.
Release Notes:
Version 2.2.0 - 2020-08-05
- Created allow list for hidden dropdown options
47 Comments
RichL I'm sorry but this field is not in there that would be too easy !
anybody or someone at zendesk can help me to hide this field "linked problem"
Hi Frédéric! I see now...wasn't familiar with this system field.
Looks like "Linked Problem" will conditionally appear when you choose to label the ticket as an "Incident". I'm not sure what benefits using the Type field would have if you aren't going to use the Linked Problem feature. So you might want to consider just removing the "Type" field from your ticket form(s).
But if you want to use the "Type" to label tickets as Incidents and not use "Linked problem" you can hide Linked Problem with the ticket field manager app by hiding the field problem:
Thank you but I only want to hide the field "linked problem" that's it.
Hi Ahn Letran
I think I stumbled upon a snag, I wanted to use the app to have more control over light agents filling out forms (internal support forms) by using the required fields to insure they filled out all necessary information and I made the app 'available' to all light agents, but then if a full agent filled out a ticket, but left a required field ( for light agents ) blank, when the light agent tries to even add an internal note to that ticket, they get blocked by the app since a required field is empty, but as a light agent, they don't have the ability to fill in that field? Is there a work around for this?
Hi William,
If I understand correctly, you have a field that is hidden for light agents, but that is also set as "mandatory" for your agents to fill in, therefore preventing your light agents from submitting any changes to the ticket if the field is empty?
Does this field need to be mandatory/hidden from the light agents?
The main workaround here that I could see would be to add a warning when a mandatory field is hidden, as we cannot override the field being set as "hidden".
-JC
Hello,
I have multiple sub-options in my dropdown options which I have added to the JSON. However the overarching option is still showing. Ex: I have a Network/Internet option, and two sub options underneath. I added the sub-options to the JSON. There is no tag for the overarching option. When testing I see the overall option, but it is blank when clicking on it. Solutions?
Neil Gloudemans - If you're trying to hide values used in a nested drop-down menu, you'll need to remove the double colon's in order for the categories hidden as well.
Category::Sub-category::Item -> Category:Sub-category:Item
Chris Fassano None of my tags have the colons. Do you mean I have to edit the field itself?
Neil Gloudemans - Yes. If the value has double colons in it to create a nested menu, then you'll need to remove the double colons.
Chris Fassano These items are no longer nested then. That will not work, as the nested items are needed by others, and need to remain nested.
Does anyone know what this error means? "Cannot read properties of null (reading 'map')"
Bill Reed,
This issue will require some investigation on our end. I have created a ticket and one of our Advocates will reach out to you via email.
Hi all,
can we use the App to hide the "TicketSkills" field? There seem to be no documentation of how this field is (internally) named and we don't manage to hide it at all. We don't want Skills to be shown (especially as we currently don't use them).
Thanks
Oliver
If you are talking about the system field "Skills", you have an option to hide it by following the steps in this article: https://support.zendesk.com/hc/en-us/articles/4408838892826-Using-skills-based-routing#topic_utt_h3x_jdb (By default, only administrators can see and update the skills field. You can configure the visibility and permissions for the skills field, so agents can view or update it as well). You have the following options:
If you have a custom ticket field created named "TicketSkills", you can hide the custom ticket field by inserting the field ID in the Hidden section as instructed in this article.
I hope it helps,
Customers in this comment thread might find this feature requests important.
Deactivate field values instead of deleting them
Please take a look and upvote if you'd like to see this change added to Zendesk.
Hi Dave Dyson
This app is great and I have it working successfully for what we need, I'm just wondering can you have this app hide two or more fields? or does it only hide one field at any one time.
I have 5 departments and currently hiding a unique filed from all departments except one department as this field is unique to them. So now only the fee's department can see this form, this works great.
I also have another department lets call it the careers department that have a different unique field and I want to also hide this one from every other department also except the careers department.
I don't see the option to have multiple hidden forms in this app?
You can hide more than one field, but the "Allowed groups for hidden fields" setting does apply to all the hidden fields -- you can't configure that separately for each hidden field, unfortunately. If you'd like, please add your use case as a comment to this post: Ticket Field Manager app - official feature request thread
Thanks!
Please sign in to leave a comment.