scott.patterson
-
Total activity71
-
Last activity
-
Member since
-
Following1 user
-
Followed by0 users
-
Votes42
-
Subscriptions16
Activity overview
Latest activity by scott.patterson-
scott.patterson commented,
Hey there, I'm wondering if I could get some help setting up similar scripts as the users here, but instead of checking the value of a text box/dropdown in the criteria to show/hide things, inste...
-
scott.patterson commented,
The way we get around this (though there may be an easier way) is tag every ticket for the shared organisation. So we have a trigger set up like: When ticket does not contain tag 'from_company_x'...
-
scott.patterson commented,
Hey all, Just adding an FYI here, but came across the comments in this article which can help to lead to a solution to hide additional text/text lines on forms: https://support.zendesk.com/hc/en-...
-
scott.patterson commented,
Just updating that Brett is correct, I tested this wrong. For Multi-Select: {{ticket.ticket_field_option_title_<ID>}} - Outputs the name of the selections {{ticket.ticket_field_<ID>}} - Outputs t...
-
scott.patterson commented,
Hey Brett, Edit: Apologies I had a mistake in my tests. This works flawlessly, thanks for your article! Thanks, -SP
-
scott.patterson commented,
What is the correct placeholder for a custom Multi Select field? Both 'ticket.ticket_field_<field ID number>' and 'ticket.ticket_field_option_title_<field ID number>' do not seem to work.
-
scott.patterson commented,
Trying to get this working, but it seems to be failing on the placeholder. Even just putting the placeholder into an internal note on a ticket to test (like: {{ticket.ticket_field_option_title_3600...
-
scott.patterson commented,
Hey all, Did anyone figure out a way to show/hide these kinds of headers based on conditional fields? Similar to what Matthew, Kristos and Brendan were attempting earlier. Currently I have a pretty...
-
scott.patterson commented,
Hi all, This would be great for me as well. My use case is: We have a couple of different incoming addresses, and we want to apply different trigger logic depending on how these tickets come in...
-
scott.patterson commented,
Hi all, I agree with the other comments here, in that it doesn't seem like a major overhaul to fix (all the functions already exist, workarounds exist, and apparently a beta exists?), with a few ...