Implemented Suggested 9/28/2020 by Hector Bas

8

votes

Merge Users & User API request

As follow-up requests to idea 15276:

We could use a merge user bulk option from the "../Admin/Users" page. When merging, a prompt should ask you which one to make the "main" profile, and all others become secondary email addresses. All tickets (and other records) should then be re-linked to the selected main user profile. I'm guessing that the losing merged user profiles would then need to be deleted in order for things to function right, but if we could just disable them and have the new ticket process just search through secondary email address fields PRIOR to seeing if the incoming email is from a disabled user, then we won't need to delete these user accounts. Although I can see the benefit of both sides (deleting to reduce clutter OR keeping for historical/logging purposes).

API requests:
  1. If added, please expose the user merge operation via the API
  2. For the "CreateUser" and "UpdateUser" endpoints, please include the secondary email address fields as inputs for inserting/updating
  3. For the "Users", "UserByUserName", and "UserByEmail" endpoints (and others that return user information), please include the return of the secondary email address field in the result payload.
  4. For the "UserByEmail" endpoint, please consider adding a boolean option to indicate whether to search through secondary email addresses or not.
avatar
Alex 6/12/2024 11:59 AM Tech
We've added Secondary emails to the /user endpoint and moved the rest of the suggestion to our internal github for reviewing I'm closing this idea now

Log in to comment...