diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-09-20 16:18:24 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-09-20 16:18:24 +0300 |
commit | 0653e08efd039a5905f3fa4f6e9cef9f5d2f799c (patch) | |
tree | 4dcc884cf6d81db44adae4aa99f8ec1233a41f55 /.gitlab/issue_templates/InfraDev.md | |
parent | 744144d28e3e7fddc117924fef88de5d9674fe4c (diff) |
Add latest changes from gitlab-org/gitlab@14-3-stable-eev14.3.0-rc42
Diffstat (limited to '.gitlab/issue_templates/InfraDev.md')
-rw-r--r-- | .gitlab/issue_templates/InfraDev.md | 56 |
1 files changed, 56 insertions, 0 deletions
diff --git a/.gitlab/issue_templates/InfraDev.md b/.gitlab/issue_templates/InfraDev.md new file mode 100644 index 00000000000..bc0e65c3c22 --- /dev/null +++ b/.gitlab/issue_templates/InfraDev.md @@ -0,0 +1,56 @@ +<!-- +Triage of infradev Issues is desired to occur asynchronously. +For maximum efficiency, please ensure the following, so that your infradev issues can gain maximum traction. + +https://about.gitlab.com/handbook/engineering/workflow/#a-guide-to-creating-effective-infradev-issues +--> + +## Summary +<!-- +Clearly state the scope of the problem, and how it affects GitLab.com +--> + + +## Impact +<!-- +- Quantify the effect of the problem to help ensure that correct prioritization occurs. +- Include costs to availability. The Incident Budget Explorer dashboard can help here. +- Include the number of times alerts have fired owing to the problem, how much time was spent dealing with the problem, and how many people were involved. +- Link to affected incidents, and cross-reference them as related issues. +- Include screenshots of visualization from Grafana or Kibana. +- Always include a permalink to the source of the screenshot so that others can investigate further. +--> + + +## Recommendation +<!-- +Provide a clear, unambiguous, self-contained solution to the problem. +--> + + +## Verification +<!-- +Provide a method for validating that the original issue still exists. + +Having a way of checking validity can save on a great deal of back-and-forth discussion between Infradev Triage participants including Engineering Managers, Directors and Product Managers and make space for other non-resolved issues to get scheduled sooner. + +Ideally, provide a link to a Thanos query or an ELK query and clear instructions on how to interpret the results to determine whether the problem is still occurring. +--> + + +<!-- +Workflow and other relevant labels + +/label ~"severity::" +/label ~"priority::" +/label ~"group::" +/label ~"devops::" + +See also: +- https://about.gitlab.com/handbook/engineering/quality/issue-triage/#availability +- https://about.gitlab.com/handbook/product/categories/ +- https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/data/stages.yml +--> + +/label ~"infradev" +/label ~"bug" |