GitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Enterprise Small Business Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream Management GitOpsGitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Enterprise Small Business Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream Management GitOpsFollow the same General Workflow as dotcom for servicing L&R internal requests.
There is a internal requests hawk role which rotates on a weekly basis which serves as a temporary measure to make sure internal requests tagged with the following labels receive the appropriate attention from Support:
Associate Subscription Console Escalation::Customers
- Workflow to be documentedBillable Members
- Workflow instructions on templateConsole Escalation::Customers
- Workflow to be documentedEULA
- WorkflowLicense Issue
- WorkflowPlan Change Request
- WorkflowSaaS Subscription Issue
- WorkflowTrial Extension License issue
- WorkflowWhen on this role, prioritize working on internal request issues over Zendesk tickets. The general workflow guide and best practices are:
Manager Approval::Awaiting
or Status::Awaiting Confirmation
).You will continue to be responsible for any issues assigned to yourself even after you're off the role, so be mindful about working sustainably. If you need to, ask for others to help with unassigned issues – the expectation is that GitLab Support as a team should be responding timely to internal requests, not you personally as the L&R Internal Requests Hawk.
You'll only be expected to work your usual work hours while doing this role. There is a PagerDuty schedule set up solely to facilitate tracking/swapping of shifts. It is in no way an indication of actual hours of work.