Recent searches


No recent searches

[Feature Request] Add conditional rules to Ticket Fields Manager app



Posted May 30, 2024

Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. 

It would be helpful if the Ticket Fields Manager app had conditional rules for hiding or showing fields and dropdown values. This app is in use by Agents.

 

What problem do you see this solving?

Right now, the Ticket Fields Manager app has an all-or-nothing approach to hiding fields and values; you can whitelist groups, but it allows those groups access to all hidden items (per type of object hidden, e.g. ticket field). Conditional rules could allow you to hide fields or values by certain group memberships instead of all groups.

 

When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business?

This is not a problem per se, but rather would be a very convenient extension in functionality. We currently have to overengineer business rules to emulate workflows that would be made easier by simply hiding them from agents who should not have access (but allowing them to be seen by those who should).

 

Are you currently using a workaround to solve this problem? (If yes, please explain)

N/A. There is a 3rd-party app which provides similar functionality by Leafworks but it can be cost-prohibitive, where the Ticket Fields Manager app is free.

 

What would be your ideal solution to this problem? How would it work or function?

The Ticket Fields Manager app would allow conditional/more narrowly defined group memberships for showing and hiding objects. For example, the JSON body for hiding dropdown values works off of a field ID key and a value key. A third key could be introduced, such as visible_to or hide_from, which would allow an administrator to specify group ID(s) that should match. In the event an agent falls in a condition where they are in one group which shows, and another group which hides, the more restrictive control would win.


0

1

1 comment

image avatar

Shawna James

Community Product Feedback Specialist

Hey Sam,
 
Thank you for taking the time to provide us with your feedback, great to see these feature requests coming through. This has been logged for our PM team to review. For others who may be interested in this feature request, please add your support by upvoting this post and/or adding your use case to the comments below. Thank you again!

0


Please sign in to leave a comment.

Didn't find what you're looking for?

New post