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 GitOpsSupport-Ops utilizes Time Tracking in the issues/MRs we work. We utilize this time tracking to help define our hiring model, measure workload, and etc. As you work issues and merge requests, make sure you utilize this feature.
At least once a day, Support-Ops should triage the issues and MRs that appear under the support-ops group.
Support-Ops also makes use of the GitLab Triage Gem to assist in ensuring all issues/merge requests are triaged.
For a list of the labels we use and what they mean, please see the Support Ops Project README
Our changelog is auto-generated once a day. It locates issues and MRs using the quarter's epic milestone. The format of these is FYxxQy.
When working issues/MRs, make sure to apply the correct epic/milestone. You can do this during creation, using the right-hand side panel, or via a comment on the issue/MR. Examples of doing this via a comment can be seen below:
What to do | Comment box text |
---|---|
Add issue to epic FY22Q1 | /epic &3 |
Add MR to milestone FY22Q1 | /milestone %FY22Q1 |