Brad Allen

I use my premium sandbox as a training environment. Unfortunately over the year and a half since we created our sandbox we have made multiple changes to our production instance that now makes our sandbox less helpful for training. In order to make this sandbox a functional training environment, it required us to make several updates to other systems to recognize the field IDs, sandbox subdomain, etc. I want to refresh this, but doing so means we will have to rebuild all of those connections that rely on field ID.

Allow for an option to refresh a sandbox, ie pull in new triggers, fields, options on existing fields rather than deleting and rebuilding from scratch. 

@... hopefully this is coherent :-) - I'm interested ultimately in making the data that i associate with a user via custom objects reportable. I can make a relationship field in my custom object to tie the object to an end user, so it shows up in Related. But, tying that end user to the custom object for reporting purposes in Explore, means i need a relationship field on the user or on the ticket that ties to that custom object record. Additionally i'd like to trigger action on a ticket based on a custom object being associated with the user. But as far as i can tell i can only do that if it's something in the ticket or user as a relationship field. I can't associate the user to the custom object in the relationship field without making a separate API call to do so, using bulk user update (limited to 2k rows at a time), or manually doing it one by one. 

The use case, i'm specifically considering right now is this: My engagement team using Braze, emails a list of users a certain communication/important update about their account. There may be 10 different versions of this, so i want to associate that list and the group they're in to the user. I can currently do this by using the API (my rudimentary API prowess lets me run a script that will take a week or 2 to do this) or i can break up a list of 1million customers into 500(ish) separate CSVs to load 1 by one into the bulk user update page.  Meanwhile data importer will let me input much larger lists to populate custom objects, but i can't use that data in reporting or triggers, unless additional action is taken at the User or Ticket level, which we could do with a webhook(i think). The other way to solve my issue would be to simply allow larger lists to be uploaded for user update/create.

Is there an ETA on when this will include actions like webhook?

When merging tickets, the experience is very inconsistent. Sometimes, it shows me the current requester's other tickets. Sometimes, it shows me the last ticket i worked on(probably because i'm multitasking and went away from Zendesk for a few minutes). 

Why not always show me this requester's other tickets? Why the delay on the tickets i've recently accessed(is this similar to the search API delay)?

Two questions related to this. 

1 - what version of jquery must be installed to use this code?

2 - does this just need to be added to the script.js file in templates or do i need some HTML in my new requests template as well?