User Mapping - UX
Problem to solve
In the process of mapping users' contributions during direct transfer, users are required to set a public email on the source instance and create a corresponding user in the destination instance with the same email address. If a user from the source instance cannot be matched to a user in the destination due to various reasons, such as the absence of prior creation, email configuration issues, or user inactivity, the import process assigns the importing user as the author or assignee for objects like issues, epics, merge requests, comments, and more.
The current preparation step for user mapping presents several challenges. It demands substantial coordination from the importing user to ensure the correct configuration of both source and destination users.
Additionally, if a user mapping fails, it is impossible to fix it unless another migration is performed.
Intended users
- Owners of a Group in a Destination Instance
- Mapped Users
User experience goal
- Larger notes on the broader experience can be seen: &12378
Proposal
- Add context to the current import UI to let group owners know about Placeholder Users.
- Create a successful import email that will be sent to group owner that initiated migration.
- Craft a banner for the Import History Page.
- Craft a reassignment table within the members page of the Group, which can be used to reassign placeholder users to destination users.
- Basic Flow: Proposed Design | Figma File
- Keep as Placeholder Flow: Proposed Design | Figma File
- CSV Flow: Proposed Design | Figma File
- CSV Email: Proposed Design | Figma File
- Create accept / decline email for destination users to accept or decline re-assignment.
- Craft notifications for group owners when re-assignment is rejected.
Other Details:
- Statuses of Placeholders: #451028[Reassignment_Statuses.png]
- Search and Filter: #451028[Filter_and_Search.png]