Autocomplete characters
The autocomplete characters provide a quick way of entering field values into Markdown fields. When you start typing a word in a Markdown field with one of the following characters, GitLab progressively autocompletes against a set of matching values. The string matching is not case sensitive.
Character | Autocompletes |
---|---|
~
| Labels |
%
| Milestones |
@
| Users and groups |
#
| Issues |
!
| Merge requests |
&
| Epics |
$
| Snippets |
:
| Emoji |
/
| Quick Actions |
Up to 5 of the most relevant matches are displayed in a popup list. When you select an item from the list, the value is entered in the field. The more characters you enter, the more precise the matches are.
Autocomplete characters are useful when combined with Quick Actions.
Example
Assume your GitLab instance includes the following users:
Username | Name |
---|---|
alessandra | Rosy Grant |
lawrence.white | Kelsey Kerluke |
leanna | Rosemarie Rogahn |
logan_gutkowski | Lee Wuckert |
shelba | Josefine Haley |
In an Issue comment, entering @l
results in the following popup list
appearing. Note that user shelba
is not included, because the list includes
only the 5 users most relevant to the Issue.
If you continue to type, @le
, the popup list changes to the following. The
popup now only includes users where le
appears in their username, or a word in
their name.
Help and feedback
If there's something you don't like about this feature
To propose functionality that GitLab does not yet offer
To further help GitLab in shaping new features
If you didn't find what you were looking for
If you want help with something very specific to your use case, and can use some community support
POST ON GITLAB FORUM
If you have problems setting up or using this feature (depending on your GitLab subscription)
REQUEST SUPPORT
To view all GitLab tiers and features or to upgrade
If you want to try all features available in GitLab.com
If you want to try all features available in GitLab self-managed
If you spot an error or a need for improvement and would like to fix it yourself in a merge request
EDIT THIS PAGE
If you would like to suggest an improvement to this doc