Brad Rhodes

It's been more than 6 months since I posted here - are we any closer to this functionality being available? My company recently was forced into the theming update and after doing so, the hacky workaround we had used previously to provide Agents with a link to create tickets using the end-user form, no longer works - making this functionality vastly more critical than it was before.

While griping persists about experience, I remain committed to the notion that the primary need here, is in allowing forms-owners to actually require data.

There is a vast gulf between "require end users to complete before submitting" and "require agents to complete before solving" and in the gulf is a lot of frustrated consumers of forms, and creators of forms.

Can we get a zendesk response to this please?

++ Tony

I apologize if I'm being an arrogant POS here, but if I can write something to do this in an afternoon or two of Powershell, surely someone can knock it out at Zendesk somewhere in the course of 4 years?

My company would very much appreciate this as well. We get by without, but as time goes on, more and more employees end up as agents for one reason or another. The GUI change is a frustration but not a big deal, but the bigger challenge is that the Agent interface for creating a ticket doesn't enforce the same requirements as the end user form.

++ - It's a little silly this isn't available as a searchable value. The property is documented in the API reference pages, but you can't actually search for it?

I mean yes, you can pull ALL the users, or ALL the agents and have your script pull out only the Suspended = True entries, but it would be vastly more efficient to just hit the endpoint for the Suspended users only :/