gistfile1.txt

I'll throw a +1 in this as well.  Here's the somewhat convoluted situation we have:

Anyone can send us emails at support@ourcompany.com, and ZD tickets are created from that email. This works great.

We wrote a SSO app that takes advantage of ZD's remote authentication and API features. Our customers can sign up and
log into our site, and check the status of their tickets that were created from our site, or from emails they sent in.
This also works great. 

But... I've seen several instances of customers signing up to our SSO app using one email address (user@work.com), and
then sending in email tickets from a different email address (user@home.com). From ZD's perspective, these are
different users because the email addresses are different. But our user gets confused, because they only see _some_ of
their tickets in our SSO app (which is only listing the user@work.com tickets).

Now that ZD can assign multiple email addresses to a single user, this problem is partially solved. But, I can't add
the user's home email to the account associated with their work email, because the home email address "is already in
use."  I basically have to find the "home" account, reassign all the tickets to the "work" user, then delete the "home"
user, and THEN add the home email to the work user.  Yow!

In this instance, a "merge users" feature (that also combines tickets) would save our support team a ton of time. :)

I hope this is somewhat helpful when discussing such a feature. Let me know if this doesn't make sense... It's tricky
to describe. :)

Thanks!
-John