Labels
Prioritized labels 7
Drag to reorder prioritized labels and change their relative priority.
-
securityGitLab.orgIssues related to the security of GitLab or its dependencies. Please report vulnerabilities responsibly per https://about.gitlab.com/security/disclosure/
-
customerGitLab.orgIssues that were reported by Enterprise Edition subscribers. This label should be accompanied by either the 'bug' or 'feature proposal' label
-
customer+GitLab.orgFeatures and bugs reported by large enterprise customers. This label is in use by the product org, please post in #product Slack channel if you have questions.
-
typebugGitLab.orgIssues that report undesirable or incorrect behavior. See https://handbook.gitlab.com/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification
- Lock on merge
- Issues
- Merge requests
-
directionGitLab.orgIssues for important features that are on our roadmap: https://about.gitlab.com/direction/
Labels 3,835
-
appsec-sast-pingunresolvedGitLab.orgThis label is applied automatically when AppSec's SAST rules are flagged on a merge request. See https://gitlab.com/gitlab-com/gl-security/product-security/appsec/sast-custom-rules
-
appsec-sastcommentedGitLab.orgAdded when automation has detected a SAST violation of GitLab's AppSec team's rules. See https://gitlab.com/gitlab-com/gl-security/product-security/appsec/sast-custom-rules
-
appsec-sasthelpfulGitLab.orgAdd this label when AppSec's SAST rules were helpful, informative, and/or not unhelpful. See https://gitlab.com/gitlab-com/gl-security/product-security/appsec/sast-custom-rules
-
appsec-sastunhelpfulGitLab.orgApply this label if AppSec's SAST rules were unhelpful and/or incorrect. See https://gitlab.com/gitlab-com/gl-security/product-security/appsec/sast-custom-rules
-
appsecSecurity Release retroGitLab.orgDenotes issues used for the security release process retrospective in the Application Security team
-
audit_eventsdata_change_deletionGitLab.orgActions which can permanently affect the state of an instance, group, project or data are key events that we want to maintain a log of, since they generally cannot be undone.
-
audit_eventsdata_copy_or_exportGitLab.orgBecause 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_eventGitLab.orgEvents 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_tokensGitLab.orgTokens 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_configurationGitLab.orgUsers 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_permissionsGitLab.orgAnything related to escalating roles, for example users may inappropriately elevate their permissions to access other parts of the product
-
audit_eventsworkflow_or_cosmetic_changesGitLab.orgIf 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_listGitLab.orgUsed for helping organize new audit event issues. Please tag Category::Audit Events and group::compliance as well when using this label.
-
authenticationGitLab.orgIssues related to authentication, including OAuth, LDAP, and SAML: http://doc.gitlab.com/ce/integration/README.html