Labels

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.

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.

Users may try to temporarily subvert restrictive settings to avoid a compliance control or policy, which may could pose a problem in an audit.

Anything related to escalating roles, for example users may inappropriately elevate their permissions to access other parts of the product

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.

Used for helping organize new audit event issues. Please tag Category::Audit Events and group::compliance as well when using this label.

Issues related to authentication, including OAuth, LDAP, and SAML: http://doc.gitlab.com/ce/integration/README.html

Indicate that this should be auto closed. Remove it if undesired. Check https://gitlab.com/gitlab-org/quality/triage-ops

Allow MRs to be auto-merged when all required approvals are present.

attempted the first auto merge

when auto merge has been attempted 2 times , this label is automatically added

auto merge has been executed 3 times

Epics and issues related to Auto Remediation feature

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)

Used to query issues that need to be reported on for OKR's, Weekly updates, and beyond.