The Ticket Field Manager app allows an administrator to quickly hide, require, and disable certain ticket fields and drop-down options in the ticketing interface. This app only works with ticket fields.
This article contains the following topics:
Related articles:
Installation
You need to install the Ticket Field Manager app from the Zendesk Marketplace.
To install the app
- Visit the Marketplace, then use the search bar to search for the Ticket Field Manager app.
- Click the app's icon to go to the app's info page.
- Click Install in the upper-right of the page.
- Select your account and click Install.
- Configure any app settings as needed and click Install.
Configuring the app
Once the app is installed, go to Admin Center > Apps and integrations > Apps > Zendesk Support apps, hover over the Ticket Field Manager, and click the arrow near the gear icon. Them, 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 custom ticket fields, use the field ID except when specifying hidden drop-down field options which use 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 drop-down options: A comma separated list of group IDs that do not have any hidden options in drop-down applied.
-
Hide drop-down form options: Hide options for a given drop-down field. The format is
[{"name": "type", "value": "problem"}]
, or, for custom fields[{"name": "custom_field_3600152073", "value": "brushed_silver"}]
To hide multiple drop-down values including those in the same field, use the format as shown in the example below.
[{"name": "type", "value": "problem"},
{"name": "custom_field_360015592073", "value": "diamond"},
{"name": "custom_field_360015592073", "value": "nickel_plated"},
The name must be listed with the name and value for each option to be hidden, even for options in the same drop-down field. It's not possible to hide the assignee field with the Ticket Field Manager app, but you can do that with the Assignment Control app.
Available ticket fields
- requester
- collaborator
- sharedWith
- status
- ticket_form_id (the ticket form drop-down)
- tags
- type
- priority
- problem
- custom field
For a complete listing of available fields for use in the form settings, see Zendesk Support placeholders reference.
Restricting app functionality
The functionality of the app is restricted to agents and admins who have been granted access through the Enable role restrictions and Enable group restrictions settings. For more information, see Restricting app access.
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 the Required form fields. The example below includes Assignee and Tags.
Release notes:
Version 2.2.0 - 2020-08-05
- Created allow list for hidden drop-down options
102 comments
Permanently deleted user
what if i just want to hide field only for 1 group?
while the group that I have is 100 groups.
do I have to do a list for "allow hide group for" 99 groups?
is it not possible if only to hide the field for 1 group? not to grant access to 99 groups
thanks
1
Ronald Suplido Jr
Thanks for your inquiry! I will be creating a separate ticket to address your concern with the Ticket Field manager app. You can expect a follow-up email from me the soonest. Thanks!
Best,
0
Thomas Lang
Hello
We are still experiencing this.
1264158216949 is there a root cause, fix for this?
Very annoying issue.
Thank you
0
Bill Reed
The issue only occurred for us so far in one very specific circumstance and eventually went away on its own. Never did determine why it occurred.
0
Jamie Noell
Could we get an update on the message that Bill raised?
https://support.zendesk.com/hc/en-us/articles/4408893441818/comments/4488958657690
We have started facing the same issue:
"Cannot read properties of null (reading 'map')"
0
Thomas Lang
1264158216949 did you ever figure out the error that states cannot read properties of null (reading 'map')
0
Shaun Murray
I would like to hide specific groups in the Assignee field from some groups.
We have two brands and have some brand-specific groups set up. We have some agents (usually new agents still learning things) in one brand that do need to work with the second brand and would like to hide those brand-specific groups so tickets do not get sent to the wrong group on accident. I have attempted to use this app to hide the groups from the assignee field, it seems like it should work because that field is a drop-down and not a multi-select. What I don't know what are the tags for the different groups? I have tried several things similar to the group names with no success. Is what I am trying to do even possible?
I have put this under the "Hide dropdown form options" section:
[{"name": "assignee", "value": "group_name"}]
0
Jagan
Hi Mike,
This is one of the issues I reported earlier. This is annoying. We have raised a support case no progress yet.
Can someone from Zendesk prioritize this? This is very annoying.
1
Mike
https://support.zendesk.com/hc/en-us/articles/4408893441818/comments/4488958657690
Does anybod know the solution for this error?
0
Jagan
Has there been any changes to the SDK that impacts this app? We are seeing the following issue starting Monday.
Issue 1: The app takes a long time to reflect when the Form is updated. If Form A has multiple mandatory fields and Form B has none, the app shows an error for Form A after changing to Form B.
Issue 2: Throws an error around null and map frequently.
0
Sign in to leave a comment.