Deactivate field values instead of deleting them

39 Commentaires

  • Joel Hellman

    This is a pain. As OP states, removing fields will destroy your Explore reports, and looking at old tickets, will give a bad UX. 

    We use a custom private app to hide some fields in Zendesk Support as a workaround. Not great to maintain, and really should be built into the product. Our workaround only works because we don't use guide or built in web widget, the workaround would become very complicated if use those. 

    Zendesk, this is a hard problem for you customers to work around.

    Would love for this to be prioritized. 

    Part of Zendesk's USP is building powerful solution using custom fields, yet we lack this basic support for maintaining the lifecycle of our custom fields. 

    I have no idea why this is not yet in the product. Is the request not "sexy" enough? AI is cool, but I also want Zendesk to nail the basics. 

    3
  • Leonardo Santos

    A native feature to deactivate fields values is essential, I'm using "Ticket Field Manager" app but with multiple ticket forms isn't a good experience because the hidden values return if you switch them

    1
  • Predz (StarRez Inc.)

    +1 for this. We are a software company that uses a drop-down field to track Product/Module type data. We would love to deactivate legacy items without losing historical ticket data. Please can we have this. Thanks!

    2
  • Anastasia Kachanova

    +1 for this

    2
  • Jimmy Rufo
    Zendesk Luminary

    Not sure why/how this hasn't be addressed.  If there was a way to merge tags used historically, then that would at least be a workaround, but no dice.  For frame of reference, JIRA components are allowed to be deactivated, which is similar to what would be custom field usage.

    1
  • Tattie Petts

    Agree this should be an option to inactive sub-fields. Also, what happens if you rename that sub field? Does that change the past naming conventions or no?

    1
  • Tony
    Zendesk Customer Care
    Hi there,
     
    I believe that closed or archived tickets should not be updated if you change the field.
     
    Best,
     
    -2
  • Marcus Vickers

    I would also like to see this functionality incorporated. I have a request right now to deprecate some old values that aren't being used any more and have no solution to do so safely.

    1
  • Ashwin Raju
    Zendesk Product Manager

    Here's an alternate solution for this use case. Let's the example of a Product catalog. Product A and B are active and Product C is discontinued. 
    1) Create a Custom object called Product, You already have the Product Name field created for you. Add a checkbox field called Active.
    2) Set the permissions to read only for Agents. We have a new feature coming next week (to hide the list view of custom objects). This will help you to hide the list view of Products, so that your agents are not distracted by this list. On the contrary, it could be useful to know if a product has been deprecated. 
    2) Upload all your products into this object.
    3) Create a lookup field in a ticket that points to Product object. Add a filter in this lookup field to only show Products that are Active

    When you go to the Ticket, your agents will only see Product A and B .. But not C. Tomorrow, you want to add a new product - add it to the product table and it will automatically show up in the tickets (as long as it is active)
    The main advantage of this approach is the scalability and manageability of this data. You can bring in much more than 2000 products into the list (you can in fact go into the millions). You can in fact assign this responsibility of keeping this data correct to the Agent Managers or someone in Ops. 

    Having said that, I do realize that this solution does not work well when you already have a drop down and want to have the same behavior in the drop down so that your reporting doesnt get affected. But it is definitely worth considering making the switch if this is a non-negotiable use case. 

    I will anyhow add this feature as a feature request into my backlog. But given my currently backlog, it doesnt seem like we'll be able to work on it this year.

    1

Vous devez vous connecter pour laisser un commentaire.

Réalisé par Zendesk