Read only ticket field for agents | The place for Zendesk users to come together and share
Skip to main content
November 5, 2019
Parked

Read only ticket field for agents

Related products:Support
  • November 5, 2019
  • 34 replies
  • 151 views

Maybe consider to create "Read Only ticket fields for agents".

 

    34 replies

    October 22, 2020

    We use the Hide Ticket fields app for fields where we do not want the agent to update a value, but ideally we would like these hidden fields to instead be read-only for and visible to agents.

    In addition, we sync user data into Zendesk, which should not be editable in Zendesk as it's not the system of record.

    November 12, 2020

    > +1 for this - specifically for fields populated by an integration.

    This! We have many fields that are populated by integrations (which is necessary to pipe data into Zendesk Explore and other BI tools) that we don't want agents to be able to edit. Is there any advice that a Zendesk expert can provide for that usecase in the current product?

    November 16, 2020

    I've run into this as well - we have a lot of fields populated by middleware (Zapier) or by triggers. While I think this feature request is super valuable, we have found a workaround for this in the meantime:

    We added the ZD Ticket Field Manager and set some of these fields to read-only using the 'Read Only Form Fields' or 'Hidden form fields' depending on the use case.  That prevents those fields from being edited by agents as we want. For some of these we also allowed certain groups to edit the fields just for the extra flexibility. I hope that helps! 

    Ahmed14
    November 25, 2020

    +1 this feature is badly needed

    December 7, 2020

    +1 We need this to protect critical data evaluated via triggers based on other input fields. Allowing these 'protected' fields to be edited breaks the integrity of the ticket data.

    October 27, 2021

    Hi,

    Is there any update on this feature? Would also be happy to have this functionality! Thanks.

    November 17, 2021

    Hi, +1 here as well

    Charlie19
    May 4, 2022

    This is necessary +1

    Cristian16
    October 10, 2022

    Hello,  This is necessary +2

     
    October 10, 2022

    This is a must!