Stan Neumann

If you go to a view, selected one or more tickets and then leave them selected for a few minutes or longer,
and then while they are selected, another user changes one or more of those selected items so that they no longer fit the view criteria,
Then:
If you navigate to a different view and then back to the first view, then any item that no longer fits the view criteria:

•  is no longer visible in the view (this part is correct)
•  but is still selected (this is highly counterintuitive)

This is dangerous, because if I then select a few visible tickets and delete them, the invisibly selected ticket is also deleted, and I had no clue that happened.  This is not just theoretical, we've had this happen at least a  few times.

I will argue that this is a bug, but support suggested I post this here to collect comments from the community.

I'm not entirely clear what you mean by "add the emails as users" - which emails are you referring to?  (The accounts of our members, or the support account?)

My company was already an organization, and all of the people in the organization were already listed as users.  However, our primary support address is not listed in the organization (is that the email you were referring to?) and if I try to add it, I'm told I can't because it is a support address.

I'm actually wondering if we're looking at different problems - the thread you point talks about cc a support address (I assume as a CC reply on an existing ticket), but my problem happens earlier - If I cc the main support address (support@mydoman.org) from the very original email in the email system before the ticket is ever created, a ticket is created but suspended.

To start with the use case:  it's not uncommon that we need to initiate an email to one of our customers (e.g. "Let us know when you have logged off the virtual machine so that we can expand the memory").  We want to send that from our primary support email (support@mydomain.org) so that any replies will be delivered to Zendesk.  But we'd also like to copy zendesk with a CC copy of that original email so that we have a ticket in Zendesk to track the communication, particularly so that we can follow up if we get no response).

Unfortunately, at the moment, because that initial email has a reply address of the primary support address, the ticket is suspended.  This means that today we simply do not include support@mydomain.com as a cc address; if the user replies, we get a ticket, but we need to track this communication separately to cover the case that the user does NOT reply and needs followup.  And of course having separate systems to track follow-ups is less than ideal!

My proposal - if the domain of the support address is included on the white-list of allowed domains and addresses, this would override the suspension of messages from  the support address.  Or perhaps we could be a bit more specific, if the individual email for the support address is in the white-list, this bypasses the suspension.
Less desirable alternative: if there was some keyword that we could place into the message that would tell the code determining whether to suspend the ticket that this was intentional, then that could be the trigger for the override.  Something like "action:create_zendesk_ticket" would virtually never occur naturally in a message (avoiding false positives); if we embedded it by hand in our email signature, it wouldn't be too obtrusive to the recipient of the email.