The value should be in the format of &epic, group&epic, or a URL to an epic ( introduced in GitLab 12.1). parent_epic No No Yes Set parent epic to. Before moving the issue, make sure it does not contain sensitive data. Be careful when moving an issue to a project with different access rules. move Yes No No Move this issue to another project. milestone %milestone Yes Yes No Set milestone. Depending on the project setting, this may be when the pipeline succeeds, or adding to a Merge Train. Label names can also start without a tilde ( ~), but mixed syntax is not supported. label ~label1 ~label2 Yes Yes Yes Add one or more labels. For example, to set the Late in July iteration: /iteration *iteration:'Late in July' ( introduced in GitLab 13.1). iteration *iteration:'iteration name' Yes No No Set iteration. This action is behind feature flag issue_email_participants and is not yet supported in issue templates. invite_email email1 email2 Yes No No Add up to six email participants. Valid options for are on_track, needs_attention, and at_risk ( introduced in GitLab 14.7). health_status Yes No No Set health status. The value should be in the format of &epic, group&epic, or a URL to an epic. duplicate Yes No No Close this issue and mark as a duplicate of another issue. Examples of valid include in 2 days, this Friday and December 31st. draft No Yes No Toggle the draft status. create_merge_request Yes No No Create a new merge request starting from the current issue. copy_metadata Yes Yes No Copy labels and milestone from another issue in the project. copy_metadata Yes Yes No Copy labels and milestone from another merge request in the project. confidential Yes No No Make confidential. Does not copy comments or system notes unless -with_notes is provided as an argument. Copies as much data as possible as long as the target project contains equivalent labels, milestones, and so on. clone Yes No No Clone the issue to given project, or the current one if no arguments are given ( introduced in GitLab 13.7). clear_health_status Yes No No Clear health status ( introduced in GitLab 14.7). The value should be in the format of &epic, group&epic, or a URL to an epic ( introduced in GitLab 12.0). award :emoji: Yes Yes Yes Toggle emoji award. assign_reviewer me or /reviewer me or /request_review me No Yes No Assign yourself as a reviewer. assign_reviewer or /reviewer or /request_review No Yes No Assign one or more users as reviewers. assign Yes Yes No Assign one or more users. approve No Yes No Approve the merge request. Command Issue Merge request Epic Action /add_contacts Yes No No Add one or more CRM contacts ( introduced in GitLab 14.6). Some quick actions might not be available to all subscription tiers. The following quick actions are applicable to descriptions, discussions, and Autocomplete handles this, and the insertion ), ampersand ( &) or at ( are case-sensitive. Underscore ( _), hyphen ( -), question mark ( ?), dot (.( '), unless it contains only these characters: If you manually enter a parameter, it must be enclosed in double quotation marks With quick actions to help users enter parameters, by providing a list of Properly detect and execute the commands. These commands in the descriptions or comments of issues, epics, merge requests,īe sure to enter each quick action on a separate line to allow GitLab to Quick actions are text-based shortcuts for common actions that are usually doneīy selecting buttons or dropdowns in the GitLab user interface. The rebase quick action was introduced in GitLab 13.8.into a description or comment field, all available quick actions are displayed in a scrollable list. Introduced in GitLab 13.8: when you enter.Quick actions when updating the description of issues, epics, and merge requests. Once an action is executed, an alert appears when a quick action is successfully applied.

Tableflip discord