Display gender pronouns in user popover
📖 What does this MR do?
Related to #333042 (closed)
In !63221 (merged) we added support for displaying gender pronouns on your profile. This MR adds support for displaying the gender pronouns on the user popover that is shown when hovering over a user's name in issues and MRs. In the process of adding gender pronouns to the popover this MR also adjusts the styling of the "(Busy)" text. This adjustment is so that it looks better next to the gender pronouns. This change to the "(Busy)" text affects the MR assignee as the component that was changed is shared between assignees and user popover.
💻 Local testing
- Navigate to
/-/profileand set your pronouns - Navigate to an issue or MR that you have commented on
- Hover over your name
📷 Screenshots
| View | Before | After |
|---|---|---|
| User popover - pronouns set |  |
 |
| User popover - "Busy" and pronouns set |  |
 |
| User popover - "Busy" and pronouns not set |  |
 |
| MR assignee |  |
 |
🚦 Does this MR meet the acceptance criteria?
Conformity
-
I have included a changelog entry, or it's not needed. (Does this MR need a changelog?) - [-] I have added/updated documentation, or it's not needed. (Is documentation required?)
-
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) - [-] I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
-
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. - [-] This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. - [-] I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec - [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
- [-] Security reports checked/validated by a reviewer from the AppSec team