Labels
Prioritized labels 0
Drag to reorder prioritized labels and change their relative priority.
Labels 3,952
-
feedbackdocs-not-helpfulGitLab.com / GitLab Support TeamDocumentation unhelpful to customer and/or Support Engineer
-
feedbackextended-TTR-caused by-technical-complexityGitLab.com / GitLab Support TeamThe ticket time to resolve was extended due to the technical complexity of the issue
-
feedbackextended-TTR-due-to-troubleshootingGitLab.com / GitLab Support TeamThe ticket time to resolve was extended due to troubleshooting requirements of the issue
-
feedbackmissing-info-by-engineerGitLab.com / GitLab Support TeamSupport Engineer did not provide adequate information to customer
-
feedbackmissing-info-from-customerGitLab.com / GitLab Support TeamCustomer did not supply enough information for investigation
-
feedbacknew-product-issueGitLab.com / GitLab Support TeamEncountered Product problem; new Issue and/or MR filed
-
feedbackoutside-supportGitLab.com / GitLab Support TeamProblem internal to Gitlab but not directly by Support
-
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