Engineering / ENG-1688
Merge duplicate people
Description
Shaped in Emargen: Merge duplicate people. Product page: Confluence PROD › Merge duplicate people.
Why
A sign-in through single sign-on is matched to a person by email. When the email we hold differs from the person's username in Entra ID or Okta, they can't sign in, and someone usually makes them a new account. Then there are two records: the old one with their roles and requests, the new one they sign in with. Vossberg has about 300 after moving to Okta (SUP-1113, SUP-1132). Support fixes them by hand.
What we build
- People › Possible duplicates: pairs with the same name at the same home depot, or the same phone number or employee number.
- An administrator picks the record to keep. The other's roles, depot assignments, waiting requests, history and sign-in move to it, and the other is removed.
- Every merge written to the audit log with both records. A merge can't be undone.
Not in this epic
- Merging without an administrator. Stopping duplicates before they happen.
Done when
Vossberg's administrators clear their list themselves. Target 22 September.
Child issues
- ENG-1689 People › Possible duplicates Done
- ENG-1690 Merge two people into one Done
- ENG-1691 Portal: duplicates list and side-by-side merge Done
- ENG-1692 Every merge written to the audit log with both records Done
- ENG-1722 Duplicates: match phone numbers however they are written Done
- ENG-1737 Merging moves waiting requests but drops who they wait on Done
- ENG-1740 Merge: moved requests come back as new Done
Linked issues
- relates to SUP-1113 Vossberg: about 300 people twice in the portal after Okta sign-in Done
- relates to SUP-1132 Vossberg: 9 more double accounts at Kassel after Okta sign-in Done
- relates to SUP-1180 Vossberg: list of the duplicate people still left Done
- relates to SUP-1186 Parcelwise: which record survives a merge? Done
Live. Bettina merged 64 pairs this afternoon. Closing.