GitLab quick actions

Version history
  • Introduced in GitLab 12.1: once an action is executed, an alert appears when a quick action is successfully applied.
  • Introduced in GitLab 13.2: you can use quick actions when updating the description of issues, epics, and merge requests.
  • Introduced in GitLab 13.8: when you enter / into a description or comment field, all available quick actions are displayed in a scrollable list.
  • The rebase quick action was introduced in GitLab 13.8.

Quick actions are text-based shortcuts for common actions that are usually done by selecting buttons or dropdowns in the GitLab user interface. You can enter these commands in the descriptions or comments of issues, epics, merge requests, and commits.

Be sure to enter each quick action on a separate line to allow GitLab to properly detect and execute the commands.

Parameters

Many quick actions require a parameter. For example, the /assign quick action requires a username. GitLab uses autocomplete characters with quick actions to help users enter parameters, by providing a list of available values.

If you manually enter a parameter, it must be enclosed in double quotation marks ("), unless it contains only these characters:

  • ASCII letters
  • Numbers (0-9)
  • Underscore (_), hyphen (-), question mark (?), dot (.), ampersand (&) or at (@)

Parameters are case-sensitive. Autocomplete handles this, and the insertion of quotation marks, automatically.

Issues, merge requests, and epics

The following quick actions are applicable to descriptions, discussions, and threads. Some quick actions might not be available to all subscription tiers.

Command Issue Merge request Epic Action
/add_contacts [contact:email1@example.com] [contact:email2@example.com] Yes No No Add one or more CRM contacts (introduced in GitLab 14.6).
/approve No Yes No Approve the merge request.
/assign @user1 @user2 Yes Yes No Assign one or more users.
/assign me Yes Yes No Assign yourself.
/assign_reviewer @user1 @user2 or /reviewer @user1 @user2 or /request_review @user1 @user2 No Yes No Assign one or more users as reviewers.
/assign_reviewer me or /reviewer me or /request_review me No Yes No Assign yourself as a reviewer.
/attention @user1 No Yes No Request attention to a merge request from a user.
/award :emoji: Yes Yes Yes Toggle emoji award.
/child_epic <epic> No No Yes Add child epic to <epic>. The <epic> value should be in the format of &epic, group&epic, or a URL to an epic (introduced in GitLab 12.0).
/clear_health_status Yes No No Clear health status (introduced in GitLab 14.7).
/clear_weight Yes No No Clear weight.
/clone <path/to/project> [--with_notes] Yes No No Clone the issue to given project, or the current one if no arguments are given (introduced in GitLab 13.7). Copies as much data as possible as long as the target project contains equivalent labels, milestones, and so on. Does not copy comments or system notes unless --with_notes is provided as an argument.
/close Yes Yes Yes Close.
/confidential Yes No No Make confidential.
/copy_metadata <!merge_request> Yes Yes No Copy labels and milestone from another merge request in the project.
/copy_metadata <#issue> Yes Yes No Copy labels and milestone from another issue in the project.
/create_merge_request <branch name> Yes No No Create a new merge request starting from the current issue.
/done Yes Yes Yes Mark to do as done.
/draft No Yes No Toggle the draft status.
/due <date> Yes No No Set due date. Examples of valid <date> include in 2 days, this Friday and December 31st.
/duplicate <#issue> Yes No No Close this issue and mark as a duplicate of another issue. Also, mark both as related.
/epic <epic> Yes No No Add to epic <epic>. The <epic> value should be in the format of &epic, group&epic, or a URL to an epic.
/estimate <time> Yes Yes No Set time estimate. For example, /estimate 1mo 2w 3d 4h 5m. Learn more about time tracking.
/health_status <value> Yes No No Set health status. Valid options for <value> are on_track, needs_attention, and at_risk (introduced in GitLab 14.7).
/invite_email email1 email2 Yes No No Add up to six email participants. This action is behind feature flag issue_email_participants and is not yet supported in issue templates.
/iteration *iteration:"iteration name" Yes No No Set iteration. For example, to se