About ticket fields

Have more questions? Submit a request

96 Comments

  • Brett - Community Manager
    Comment actions Permalink

    Yikes! Thanks for sharing that C F :)

    I did not realize those were switched around above.

    I'll pass this feedback along to the appropriate team to get corrected.

    I appreciate you taking the time to share this with us!

    0
  • Amy Malka
    Comment actions Permalink

    Brett and C F, I’ve updated this article so that, hopefully, this clears up the confusion over the definitions for Incident and Problem. Thanks for the feedback!

    0
  • Nicole Chan
    Comment actions Permalink

    Hi, 

    We had disabled the standard "Type" field and create the custom field to replace "Type" field in Zendesk, and the Zendesk is integrated to SFDC, how can I shows the custom field instead of standard Type field in SFDC, as all tickets type shows as "Incident" which is very misleading to our sales rep. thanks.

    0
  • Dan Cooper
    Comment actions Permalink

    Hi Nicole, 

    I've had this challenge in the past as well.  I am not a fan of incident being the default option when the Type field is disabled.  However, you could enable the field and just remove it from your forms.  Then you can use a trigger to set the value that you want on ticket creation behind the scenes so it displays more appropriately in Salesforce.

    0
  • Heather Cook
    Comment actions Permalink

    The field "organisation" pops up when the end user is linked to more than one organisation. Can i rename this field? As the word organisation doesn't mean much to my customers.

    0
  • Devan - Community Manager
    Comment actions Permalink

    Hello Heather Cook,

    So via the base client, this would not be able to be edited as you described. You could edit this via the API through custom code, which I've gone ahead and linked an article below that goes into the basics of this. I would also suggest posting this idea in our Support Product Feedback forum so our developers can consider this for potential future updates.

    Support API

    Best regards. 

    0

Please sign in to leave a comment.

Powered by Zendesk