<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=395631) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the \\\`What does success look like, and how can we measure that?\\\` section. \\--> When commenting on an issue/merge request when we type `@` a dropdown is presented to quickly search users you want to mention. This causes lookups in the backend as searches. However, the most common scenarios (we theorize, could be confirmed) is to address other already-known participants: Authors, Assignees, Reviewers... So how about we add: ``` @_authors @_assignees @_reviewers ``` programatically, always immediately visible in the @ dropdown, that would expand to the proper list of users upon selection (not upon submission, so the backend would never see these). Any hurdles for this? ### Screenshots | Loading (now) | Loading (proposal) | |---------------|--------------------| |  |  | ### Details The search is already limited to participants and that's still useful. But this would allow the `@` dropdown to be context-aware of which page it's on and repurpose the data already loaded elsewhere for faster resolution. <!-- Label reminders Use the following resources to find the appropriate labels: \\- Use only one tier label choosing the lowest tier this is intended for \\- https://gitlab.com/gitlab-org/gitlab/-/labels \\- https://about.gitlab.com/handbook/product/categories/features/ \\-->