Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitaly.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPatrick Steinhardt <psteinhardt@gitlab.com>2022-05-17 13:26:37 +0300
committerPatrick Steinhardt <psteinhardt@gitlab.com>2022-05-17 13:26:37 +0300
commitab0e402a9e910d99b13ef3f1631844d5fa386c97 (patch)
treeb62be41cf930d814a900ad1a093c07f001178e19
parent93762b621c011fe570339c1c247d5197c2cfefcc (diff)
parent1f1f768306eafc0e60231408cc8fae44a40c25e4 (diff)
Merge branch 'ahorvath-customer-issue' into 'master'
Update "Support Request" template in line with Gitaly's intake workflow. See merge request gitlab-org/gitaly!4552
-rw-r--r--.gitlab/issue_templates/Support Request.md10
1 files changed, 8 insertions, 2 deletions
diff --git a/.gitlab/issue_templates/Support Request.md b/.gitlab/issue_templates/Support Request.md
index 907083cc8..e9e10aee2 100644
--- a/.gitlab/issue_templates/Support Request.md
+++ b/.gitlab/issue_templates/Support Request.md
@@ -10,10 +10,14 @@ As we collaborate on resolution of this issue, the Gitaly team will attempt to u
_The goal is to keep these requests public. However, if customer information is required to the support request, please be sure to mark this issue as confidential._
+This request template is part of [Gitaly Team's intake process](https://about.gitlab.com/handbook/engineering/development/dev/gitaly/#how-to-contact-the-team).
+
## Customer Information
**Salesforce Link:**
+
**Installation Size:**
+
**Architecture Information:**
<!-- Please include cloud hosting provider if available, links to architecture documents, etc... -->
**Slack Channel:**
@@ -28,6 +32,8 @@ _The goal is to keep these requests public. However, if customer information is
<!-- Please be as realistic as possible here. We are sensitive to the fact that customers are frustrated when things aren't working, but realistically we cannot treat everything as a Severity 1 emergency.
For a good rule of thumb, please refer to the bug prioritization framework located in the handbook here: https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity
+
+For S1 or S2 issues, please follow https://about.gitlab.com/handbook/engineering/development/dev/gitaly/#urgent-issues-and-outages .
-->
### Problem Description
@@ -48,5 +54,5 @@ For a good rule of thumb, please refer to the bug prioritization framework locat
- [ ] Severity realistically set
- [ ] Clearly articulated what is needed from the Gitaly team to support your request by filling out the _What specifically do you need from the Gitaly team_
-/label ~"Gitaly Customer Issue" ~"group::gitaly" ~"devops::create"
-/cc @mjwood
+/label ~"Gitaly Customer Issue" ~"group::gitaly" ~"devops::create" ~"workflow::problem validation"
+/cc @mjwood @andrashorvath