Try to match users with different display name formats when migrating capacities #1985
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hmmm... I think this change conflicts with the new User Mapping tool, and can benefit there. |
|
Isn't that user mapping tool is used when you map users with different unique id? In this case First, Last, Unique names are the same. Only Display name is different and prevents capacity migration. |
The User mapping tool maps the display name. It would be good to merge these two ideas... Ill merge this first and add something to the backlog. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Run into issue migrating capacities when user display names were different in source and destination organizations - "John Doe" vs "Doe, John". This commit is trying to match users using different display name format combinations.