From 4241782e909ac961a0352543c386194675155340 Mon Sep 17 00:00:00 2001 From: Georgiana Dolocan Date: Mon, 8 Jan 2024 13:54:07 +0200 Subject: [PATCH 1/2] Update non incident docs to not require manual triager intervention on the boards --- projects/managed-hubs/support.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/projects/managed-hubs/support.md b/projects/managed-hubs/support.md index 969c80ed..2c00c8eb 100644 --- a/projects/managed-hubs/support.md +++ b/projects/managed-hubs/support.md @@ -193,10 +193,12 @@ When a new ticket lands in Freshdesk under the support group and it is not an in 3. `Who: Support Steward` - **Open an engineering issue**. If this is a {term}`Change Request` or {term}`Guidance Request` and/or you cannot resolve the issue within 30 minutes, then open a support issue for the team to discuss. + **Open an engineering issue**. If this is an issue that cannot be resolved within 30 minutes, then open a support issue for the team to discuss. + + [{bdg-primary}`Open a Freshdesk ticket tracker issue`](https://github.com/2i2c-org/infrastructure/issues/new?assignees=&labels=&template=5_freshdesk-ticket.yml) that describes the ticket and provide as many details as possible about the results obtained in the first 30m investigation (if any). + + This issue will then be automatically added to the **Eng & Prod** board by the existing automation alongside the the **type**: `support` and the **impact** level specified in the form project fields. - [{bdg-primary}`Open a general issue`](https://github.com/2i2c-org/infrastructure/issues/new?assignees=&labels=&template=01_new-issue.yml) that describes the request and any next steps we should take. It should be automatically added to the **Eng & Prod** board by the existing automation. Add the **type**: `support` and choose an **impact** level in the **Eng & Prod** board metadata (available for the very same issue, no need to visit the board itself!). - If the issue has a `critical` impact (we defer that first evaluation to the support steward), an additional ping to the support Slack channel is needed to boost the signal. :::{admonition} What does `critical` mean? From 22849641f67de77d7c98a3c25adf4921fa618757 Mon Sep 17 00:00:00 2001 From: Georgiana Dolocan Date: Wed, 10 Jan 2024 16:08:09 +0200 Subject: [PATCH 2/2] Reword for clarity --- projects/managed-hubs/support.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/projects/managed-hubs/support.md b/projects/managed-hubs/support.md index 2c00c8eb..af0c7bc5 100644 --- a/projects/managed-hubs/support.md +++ b/projects/managed-hubs/support.md @@ -193,9 +193,9 @@ When a new ticket lands in Freshdesk under the support group and it is not an in 3. `Who: Support Steward` - **Open an engineering issue**. If this is an issue that cannot be resolved within 30 minutes, then open a support issue for the team to discuss. + **Open an issue in the 2i2c/infrastructure repository**. If this is an issue that cannot be resolved within 30 minutes, then open a GitHub issue for the team to discuss. - [{bdg-primary}`Open a Freshdesk ticket tracker issue`](https://github.com/2i2c-org/infrastructure/issues/new?assignees=&labels=&template=5_freshdesk-ticket.yml) that describes the ticket and provide as many details as possible about the results obtained in the first 30m investigation (if any). + [{bdg-primary}`Open a "Freshdesk ticket tracker" type of issue`](https://github.com/2i2c-org/infrastructure/issues/new?assignees=&labels=&template=5_freshdesk-ticket.yml). Use this to describe the ticket and provide as many details as possible about the results obtained in the first 30m investigation (if any). This issue will then be automatically added to the **Eng & Prod** board by the existing automation alongside the the **type**: `support` and the **impact** level specified in the form project fields.