Lucas

100% agree Óskar Ómarsson. It would be great for admin's to decide what should be persistent between tickets. E.g. Force the Apps option to be selected, rather then agent have to reselect when moving on to the next ticket.

@... - Perfect, thanks!

If you want to automatically display the Encoded ID without having to run a macro manually, you can use this method.

Setup a new Ticket Field

1. Create a new Ticket Field (Text) - note down the field ID
2. Add the Ticket Field to your Ticket Form

Create a HTTP Target

1. Create a new HTTP Target (Settings > Extensions) with the following settings

• URL: https://YOURDOMAIN.zendesk.com/api/v2/tickets/{{ticket.id}}.json
• Method: PUT
• Content type: JSON
• Enable Basic Authentication (failing to do this will cause the target to fail)

Create a trigger

1. Create a new trigger that will run matching your required conditions
2. Add an action: Notify Target 
3. Enter the following JSON

{
"ticket":

{
"custom_fields": [{"id": INPUTFIELDIDHERE, "value":"[{{ticket.encoded_id}}]"}]
}
}

Now each time your trigger conditions are met, the ticket will display the Encoded ID as per below.

When using the jQuery method, if no image exists for a category a blank box is displayed.

Is there a code modification which will display images if they exist in the document head, but show only the heading if there is no image.

Thanks Nicole, GDPR, Mandatory data breach reporting (in some countries) and organisation reputation risks are all really important considerations for businesses servicing multiple clients with a solution such as Zendesk. The risks of a data breach could be minimised by tighter restrictions around ticket merging.  I will take your advice and contact privacy@zendesk.com and encourage others to do the same.

@Oren - Did you get any further response? I agree, not sure how security is a feature request and not a high priority. For organisations that support multiple customers this is one real product weakness within Zendesk.

@Zendesk community managers - is any work being done on this or at least workarounds?

Thanks @Nicole.

I know how it is, but we have to nudge sometimes :)

Have a great day.

Thanks Nicole, 6 years to the date this was suggested and this basic functionality has not been introduced. #sadface

There are some workarounds available for those that want to remove all CC's or you could modify i guess for select CC's.

https://support.zendesk.com/hc/en-us/community/posts/209285958-Removing-ALL-CCs-from-a-ticket-via-a-Trigger-Target 

Disclaimer: It's not officially supported, which brings us back to... It's been 6 years - can some one work on this and make some #smileyfaces

+1 - as per previous commentators, it would be good to see a reply from Zendesk on this feature. 

At the very least a warning should be displayed, if not outright prohibited.