Labels
Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 3,988
-
feedbackprocess-confusing-customerGitLab.com / GitLab Support TeamCustomer found support process confusing or unclear
-
feedbackprocess-does-not-existGitLab.com / GitLab Support TeamProblem does not have an existing Support process
-
feedbackprocess-engineer-not-followedGitLab.com / GitLab Support TeamSupport Engineer did not follow documented support process
-
feedbacksoft-skillsGitLab.com / GitLab Support TeamSupport Engineer responses unhelpful or customer expectations mishandled
-
feedbacktechnical-skills-customerGitLab.com / GitLab Support TeamCustomer lacks skills or permissions to troubleshoot or resolve problem
-
feedbacktechnical-skills-engineerGitLab.com / GitLab Support TeamSupport Engineer lacks skills or permissions to troubleshoot or resolve problem
-
feedbackunable-to-fulfil-customer-expectationsGitLab.com / GitLab Support TeamSupport are unable to fulfil the request according to the customers expectations
-
field communicationsGitLab.comitems that include work by/with the Field Communications team under Field Enablement
-
field enablementGitLab.comthe starting point label for issues, templates, etc. that involve the Field Enablement team
-
field eventsGitLab.comlabel for Field Enablement-supported events (e.g. QBRs, SKO, President's Club, etc.)
-
firedrillGitLab.comCollection of issues that describe scenarios we'd like to showcase to the entire team.