Add "GitLab Team Member" badge to Issues/MRs/Epics list view and headers
What does this MR do?
See #212259 (closed)
Adds "GitLab Team Member" badge to Issues, MRs, and Epics created by a user with a @gitlab.com email. Badge added to the list view for all three, and header for Issues and MRs (see here !28359 (merged) for Epic header).
Screenshots
| Page | Before | After |
|---|---|---|
| Issue List |  |
 |
| MR List |  |
 |
| Epic List |  |
 |
| Issue |  |
 |
| MR |  |
 |
Local Testing
- Enable
:gitlab_employee_badgefeature flag.bin/rails consoleFeature.enable(:gitlab_employee_badge)
- In
lib/gitlab.rbchangeself.com?to returntrue - Create a user with a
@gitlab.comemail address - Navigate to a project, create an Issue and MR
- Install an EE license. See https://about.gitlab.com/handbook/developer-onboarding/#working-on-gitlab-ee.
- Navigate to a Group and create an Epic
Note: You may need to run gdk restart because of the caching on app/models/user.rb
Related MRs
- Epic headers - !28359 (merged)
- Issue/MR assignee and assignee dropdown - !28377 (closed)
- Issue/MR/Epic comments and notes - !28243 (merged)
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides - [-] Database guides
-
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers - [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] 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
Edited by Peter Hegman