Lou Gallo

The end user does have an API endpoint that would work.  There are two actually that you can use one is /requests and the other is /organization/:orgid/requests. I have built a proof of concept and I can get it to download to csv.  I am frustrated that zendesk has not added this as it was in the old help desk and everywhere in the Agent view you can download list data.. even in area like ticket fields for lists.  Really seems like an easy thing to add.  Once I get a working version in the handlebar template, I will come back to share.

I opened up a ticket on Monday and still have no resolution. I have already talked to Atlassian and thier logs are not even getting hit from thee proxy.. Can I get someone at Zendesk to address this soon. This is a Huge hit to our company.

I am having the same issue.. I have been fighting it now since May 15, 2022.  I have talked to Atlassian and they have not made any changes to TLS since 2021.  I think there is an issue in the proxy service. I currently have a ticket open with Zendesk but have not gotten anywhere.

I have apps that I wrote back in 2014, 2016 and 2017 that are all failing now with the proxy to JIRA.

I have tested this with a few other tools and the handshake works fine through the proxy but I think the TLS requirements might have been dropped or not upgraded recently..

https://support.atlassian.com/security-and-access-policies/docs/supported-security-protocols-for-atlassian-cloud-products/

@jordan totally correct. This can be done with the API. I do it for a few rare cases to pass tickets an email just like you can in the ticket UI. I posted this. A while back.

@Christopher Hopper

To create this you will need to provide a name for the trigger, the rules and the actions as you do in the UI.  In my example I am looking for tags but you can reference the api docs to give you the appropriate payload options for rules and actions.

Here are the details:

• POST request to endpoint:
  `/api/v2/triggers.json`
• Payload:
  `{'trigger':{'title':'

Like I posted above, I am doing this via the API so it seems the system is already setup to do such a thing.  The issue seems to be in the Edit Trigger UI since it is doing some validation on the field for add CC and will not allow end users to be added.

Seems to be a relatively trivial change from a technical approach unless there is some nefarious angle or potential circular reference problem that could put it into an infinite loop.  Although other scenarios like that are detected in Triggers already. 

If anyone needs to setup triggers for this I would be happy to share the python script or at least the endpoint and payload I am sending to it.  Since, in most cases, you "set and forget" the trigger, this might be a good workaround in the meantime.

You can set it by any userid via the API tho.  So you can set it to an end user in the ticket form and via the API but not as a trigger... seems like you need to simplify your field lookup.. Easy fix I think..

https://developer.zendesk.com/rest_api/docs/core/triggers

Just wrote a py script to do it.