Feature Request: Add "Changed", etc, trigger test for custom Drop-down ticket fields


  • Nicole S.
    Zendesk Community Team

    Thank you for taking the time to post this detailed feedback, Alex, and welcome to the Zendesk Community!

    If other users like this idea, please up-vote Alex's post and add any details you can in the comments below. 

  • Heather Rommel
    Community Moderator

    I know what you mean on this one. The only thing I can think of as a workaround is to create a new field to capture the old value of the field you want to trigger on. Then you'd need to set up a bunch of triggers to auto set the old field value.
    Them you could base your triggers on those two fields.
    Clunky but it should work.

  • Suja Socrates

    We would love to have this feature ASAP.  Now we are writing a lot of custom code to accomplish this.

  • Christopher Rehn

    This feels like a basic standard feature that would benefit us a lot.

    My workaround today is adding a tag when the trigger fires, and having that tag as a requirement for "does not exist" upon firing. However, this does not help for Triggers that may need to fire more than once, but not always.


Please sign in to leave a comment.

Powered by Zendesk