How can I reset drop-down field values for follow-up tickets?

Return to top
Have more questions? Submit a request

36 Comments

  • Jason Littrell

    I had no idea this closed ticket channel existed. Pretty cool.

    The most common request I get for follow-up tickets, though, is to assign it to the group that handled the previous ticket. Is there a simple way to do that using the closed ticket condition? I know I could probably create triggers to add tags based on the group, then create another set of triggers to read the tags on follow-up tickets and reassign the group, but that's a little too cumbersome.

    0
  • Jessie Schutz
    Zendesk team member

    Hi Jason!

    The group and requester from the Closed ticket don't get carried over to the follow-up ticket when it's created, so I'm afraid Triggers are going to be the way to go with this.

    You can create triggers to add tags based on the group if you like. Otherwise, you might consider adding a drop-down field to the ticket form and make it required for agents to fill out in order to solve the ticket. This will force them to select their group, and then you'll just need to create the Triggers based on the selections from the custom field. This would save you some time building Triggers, but it will add a little bit of work for your agents, and of course there's always the margin for error.

    Please let me know if you have any other questions!

    1
  • Matthew Searle

    I have a version of this set up with the 'Remove tags' action with a list of the tags that can be applied for our various custom fields. I found that just resetting the fields wasn't enough to wipe the tags.

    0
  • Jim Aycock

    This article is no longer accurate, I assume this is due to updates in the platform.  

    For example, The first "Meet All" condition you show is "Ticket is Closed".  In my interface "Closed" is not listed as an option for "Ticket is".  

    Does the article need updating, or am I missing something?   

    I am trying to solve the problem we have where customers continuously reply to a closed ticket email with a new issue.  It happens a lot.  

    0
  • Jessie Schutz
    Zendesk team member

    Hey Jim!

    In the screenshot the conditions are Ticket is > Created and Ticket: Channel > is > Closed ticket. I think that you might have swapped "created" with "closed" in that first condition. :) These conditions will work for you if you're trying to target new tickets that are created as follow-up tickets from a Closed ticket. Let us know if you need anything else!

    0
  • Pedro Rodrigues

    We've created two triggers: one that eliminates all tags in the follow-up (except one), turning it into a "brand new" ticket, ready to go through our normal trigger flow.

    However, we also have Facebook and Twitter integrations. When these follow-ups are created, the condition "Ticket Channel is Closed ticket" doesn't work (because "ticket channel is facebook/twitter"), so how do we get around this?

    Also asked here

    1
  • Adarsh Shet

    Hi, I have a requirement to use the "Create follow up of closed ticket" button to clone an existing ticket. As of now, I am using clone ticket feature of zendesk. but it will be easy to have an additional button in the ticket(Submit dropdown) itself. Any idea how to include this additional button in the below submit dropdown in the ticket itself. 

     

    0
  • Dan Ross
    Community Moderator

    @Pedro I think you're out of luck on this one - I also can't see any way to address follow up tickets from channel integrations.

     

    @Adarsh The only way I can think of to do this would be really involved and likely not worth the effort. We can't modify this list ourselves, but a browser extension may be able to do so. I've seen ones that modify the appearance of that menu but adding a new option entirely would be a good deal of custom work. I don't think it would be very practical, unfortunately.

    0
  • Dan Cooper
    Community Moderator

    Hi Ardash, 

    When a ticket is in a closed state, a Create follow up button presents itself.  If you are looking for a way to set a ticket to Closed so you have this option, you can create a trigger that does so.  I typically have an admin trigger that looks something like this:

    ALL

    • Ticket is updated
    • Tags contain one of the following auto-close

    ANY

    • Current user is (admin name here)

    ACTION

    • Status is closed

    This would allow you to close a ticket by adding a tag (be careful, you can't reverse this) and you'd have the create follow up ticket button available. 

    0
  • Andrew J
    Community Moderator

    @pedro, do Facebook channels actually create follow up tickets? I've never noticed it and use it all the time. Please confirm that these aren't just new tickets created from an existing post or message.

    0
  • Pedro Rodrigues

    @Andrew, they do (both Facebook and Twitter):

     

    Out of curiosity, when do you close these social integration tickets? Native 28 days?

    Because if you set to Closed a Facebook private msg after 3 days being Solved, and the end user replies afterwards, it will create a follow up.

    0
  • Brett Bowser
    Zendesk Community Team

    Hi Pedro,

    Do you have an automation that automatically closes these Facebook tickets after 3 days of being solved? If so, what if you apply a facebook_ticket_closed tag to the ticket once it's been set to closed? Then you can set up a separate trigger that removes tags from any ticket that contains this facebook_ticket_closed.

    This may not be the exact solution you're looking for but hopefully this helps!

    0
  • Pedro Rodrigues

    Yep, that's what we got in place now. Thanks!

    0
  • Brett Bowser
    Zendesk Community Team

    Awesome. Thanks for the confirmation :)

    0
  • Ed Ball

    Does the brand carry over as well as the tags and ticket fields? I do not remember if it ever did, but it does not appear to now. It comes in with the main Zendesk site and not the brand that was associated with it when the original ticket was closed.

     

    Just going to add, I did this by creating a follow up on the support page and that worked fine. But replying to an email created the follow up and it went to the correct email address, but still came in with the mothership (Main Zendesk) brand. 

    0
  • Brett Bowser
    Zendesk Community Team

    Hey Ed,

    The expected behavior is that the follow-up ticket will carry over the brand, ticket fields, and tags associated with the previous ticket. If you're experiencing anything different on your end, you may want to check the ticket events and confirm there are no triggers that are resetting these fields.

    Let me know if you have any other questions for me!

    0
  • JR

    Hey Brett Bowser!

    I can't seem to set tags to empty.

     

     

    The "Create" button remains disabled until I add at least one tag to set it to.

     

    Is there another way to clear out all the tags?

     

    0
  • Brett Bowser
    Zendesk Community Team

    Hey JR,

    What you could do is just add a follow_up tag to the ticket using Set Tags which will replace any of the previous tags set on the ticket.

    Does that get you the results you're looking for?

    Let me know!

    0
  • Paula Arakaki

    Hi All, and how can I reset a numeric or text custom field? I have a "lot number "custom field. How can I reset it in this case?

    0
  • Brett Bowser
    Zendesk Community Team

    Hey Paula,

    You can't use triggers to reset numeric or text fields at this time. You may need to use the API to reset these values on follow-up tickets.

    I'll be sure to let our product managers know of this functionality need.

    Cheers!

    0
  • Paula Arakaki

    Thanks, Brett!

    0
  • Andrew J
    Community Moderator

    You could use a http target for this I think Paula, or maybe even just a URL target.  Not sure if you can set custom field values with URL targets - but possibly.

    0
  • Jeffrey Siy

    this doesn't work for me. i followed exactly and made action a dropdown -

    when i create a new follow-up ticket it doesn't remove the tag or reset the dropdown I want

    0
  • Andrew J
    Community Moderator

    Jeffrey, are you using an http target?

    0
  • DJ Jimenez

    +1 for having the option to wipe number fields, date fields, and text fields for follow-up tickets via triggers natively. We can create an API target to have a trigger wipe them, but there are 2 issues:

    1. Using the target / trigger combo for wiping would fight with the other things using the API when tickets get created. This will increase the likelihood of a race condition happening on our incoming tickets, making these updates unreliable.
    2. We have a large number of non-drop-down fields that need to be wiped for follow-up tickets. It would be easier to keep track if we created separate triggers for each field set (ex. have CSat-related fields wiped with 1 trigger and escalation-related fields wiped with another). We can't do this currently due to #1.

    Even if we wanted to reduce the risk of a race condition by consolidating the field wipings into a singular API call during ticket creation, the API call would resolve after the ticket ran through the "ticket is created" timed triggers. This means any values that were set up by triggers would get wiped out along with the values inherited from the original closed ticket if it's made too inclusive

    1
  • Naomi Watnick

    Hi - Do you have a suggestion on how to reset a multi-select field for follow-up tickets?

    0
  • Brett Bowser
    Zendesk Community Team

    Hey Naomi,

    Since multi-select field options have a tag associated with it, you could create a trigger that fires any time a follow-up ticket is created and then use the Set Tags>follow_up condition which willy apply the follow_up tag and remove any previous ones.

    This should reset the multi-select field but could also reset any other fields that use tags as well. If that's not an issue then I would say this would be the easiest route to take.

    Let me know if you have any other questions!

    0
  • Naomi Watnick

    Thanks, Brett,

    Unfortunately there are other fields we must keep in the follow-up - and cannot reset.  Do you have other suggestions or a feature request page for this?

    0
  • Andrew J
    Community Moderator

    How many options are there for the multi-select?
    It may be possible to reset this field using a http target.

    0
  • Naomi Watnick

    Hi Andrew J There are a growing list of around 50ish in the list.

    0

Please sign in to leave a comment.

Powered by Zendesk