Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.
  • advisoryerror
    GitLab.org / GitLab CVE assignments
    An error has occurred and is being investigated.
  • advisoryrejected
    GitLab.org / GitLab CVE assignments
    Advisory is rejected by MITRE and is being investigated.
  • advisorypublished
    GitLab.org / GitLab CVE assignments
    6/6: Advisory is published and available on MITRE.
  • advisorypublishing
    GitLab.org / GitLab CVE assignments
    5/6: Advisory is submitted to MITRE and awaiting status change.
  • advisoryassigned
    GitLab.org / GitLab CVE assignments
    4/6: Advisory is assigned a CVE ID and awaiting final approval.
  • advisoryassign-cve
    GitLab.org / GitLab CVE assignments
    3/6: Advisory is reviewed and awaiting CVE number assignment.
  • advisoryreviewing
    GitLab.org / GitLab CVE assignments
    2/6: Advisory is valid and awaiting review.
  • advisoryqueued
    GitLab.org / GitLab CVE assignments
    1/6: Advisory is new and awaiting validation.
  • advisory-scheduleimmediate
    GitLab.org / GitLab CVE assignments
    Advisory is ready to be published ASAP.
  • advisory-cve-idimmediate
    GitLab.org / GitLab CVE assignments
    Advisory needs CVE number assignment ASAP.
  • submissioninvalid
    GitLab.org / GitLab CVE assignments
    Submission has semantically invalid or missing data.
  • mitresubmitted
    GitLab.org / GitLab CVE assignments
    Advisory has been submitted to MITRE.
  • submissionvalid
    GitLab.org / GitLab CVE assignments
    Submission is semantically valid.
  • advisory-schedulewait
    GitLab.org / GitLab CVE assignments
    Advisory is not ready to be published.
  • advisory-groupgitlab
    GitLab.org / GitLab CVE assignments
    Advisory relates to GitLab.
  • advisory-groupexternal
    GitLab.org / GitLab CVE assignments
    Advisory relates to an external project hosted on GitLab.
  • advisorymitre-published
    GitLab.org / GitLab CVE assignments
    Deprecated: Advisory is published and available on MITRE.
  • advisorymitre-notified
    GitLab.org / GitLab CVE assignments
    Deprecated: Advisory is submitted to MITRE and awaiting status change.

    • Other labels

  • audit_eventsdata_copy_or_export
    GitLab.org
    Because the data in an instance is very sensitive, we will record logs of actions that are used to copy, mirror, or export that data.
  • audit_eventshigh_volume_event
    GitLab.org
    Events likely to generate a high volume of data that could affect performance. This type of event could be served in Webhook-based audit events.
  • audit_eventskeys_and_tokens
    GitLab.org
    Tokens such as Personal Access Tokens can give anyone who holds them the permissions the token has. Steps done with these tokens will be logged in case a token falls into inappropriate hands and the changes made with it need to be undone.
  • audit_eventssettings_configuration
    GitLab.org
    Users may try to temporarily subvert restrictive settings to avoid a compliance control or policy, which may could pose a problem in an audit.
  • audit_eventsuser_permissions
    GitLab.org
    Anything related to escalating roles, for example users may inappropriately elevate their permissions to access other parts of the product
  • audit_eventsworkflow_or_cosmetic_changes
    GitLab.org
    If a change is made to something like a template or project label, it could potentially be disruptive to the workflow of the teams using it, so we will log those actions.
  • audit_events_list
    GitLab.org
    Used for helping organize new audit event issues. Please tag Category::Audit Events and group::compliance as well when using this label.
  • authentication
    GitLab.org
    Issues related to authentication, including OAuth, LDAP, and SAML: http://doc.gitlab.com/ce/integration/README.html
  • authn FY25 roadmap
    GitLab.org
  • authorization
    GitLab.org
  • auto closed
    GitLab.org
    Indicate that this should be auto closed. Remove it if undesired. Check https://gitlab.com/gitlab-org/quality/triage-ops
  • auto remediation
    GitLab.org
    Epics and issues related to Auto Remediation feature
  • auto updated
    GitLab.org
    Issues that have been updated in accordance with our issue triage policies (https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/contributing/issue_workflow.md)
  • auto-report
    GitLab.org
    Used to query issues that need to be reported on for OKR's, Weekly updates, and beyond.
  • automation:author-reminded
    GitLab.org
    This label keeps track of Community contribution MRs where author have been reminded to take action on their MR
  • automation:bot-authored
    GitLab.org
    Identifies merge requests that are authored by bot tooling
  • automation:bot-no-updates
    GitLab.org
    Tells bots to stop updating issues / MRs
  • automation:bug-missing-severity
    GitLab.org
    Label to prevent duplicate notes from the triage-ops bot for bugs without a severity
  • automation:devops-mapping-disable
    GitLab.org
    Allows to disable the automated stage/group label inference: https://about.gitlab.com/handbook/engineering/quality/guidelines/triage-operations/#stage-and-group-labels-inference-from-category-labels
  • automation:gitlab-housekeeper-authored
    GitLab.org
    Any merge requests authored by the automated `gitlab-housekeeper` gem https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper