Problem/Motivation

This came up in #3568006: Surface person fields on the mapped user:

Using the same field settings on the user entity, as currently set on the contact entity

Proposed resolution

When adding fields to the user in this way, should we check each contact display against each user display? If the person has the same display name as the user, we copy the field settings. If there is not a matching display the field is hidden. I am not suggesting the two be linked in some way, only which default settings to use when adding these types of fields.

Comments

svendecabooter created an issue. See original summary.

bluegeek9’s picture

bluegeek9 commented
Status: Active » Closed (duplicate)

I implemented the feature in #3568006: Surface person fields on the mapped user

I granted you credit for this issue.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.