From 40ebe14c43f1c94ea9e8e8dfcc89988d2e84ece5 Mon Sep 17 00:00:00 2001 From: many <VC6l9uBUTvTlcIjrI7sn> Date: Sun, 21 May 2023 22:43:00 +0200 Subject: [PATCH] incidence template --- .gitlab/issue_templates/incidence_template.md | 36 ++++++++++++------- 1 file changed, 23 insertions(+), 13 deletions(-) diff --git a/.gitlab/issue_templates/incidence_template.md b/.gitlab/issue_templates/incidence_template.md index 330e70bd..1afbcc50 100644 --- a/.gitlab/issue_templates/incidence_template.md +++ b/.gitlab/issue_templates/incidence_template.md @@ -1,22 +1,32 @@ -**Describe the incident** +**Summary:** -A clear and concise description of what the problem is. +Provide a brief summary of the incident. -**Describe step by step the course of the event** +**Description:** -1. Go to '...' -2. Click on '....' -3. Scroll down to '....' -4. See error +Describe the incident in detail, including the context and any relevant background information. +Explain what happened, when it occurred, and the impact it had on the project or users. -**Expected behavior** +**Steps to Reproduce (if applicable):** -A clear and concise description of what you expected to happen. +If there are specific steps that can reproduce the incident, provide them here. +This can help in diagnosing and understanding the root cause of the issue. -**Screenshots** +**Expected Behavior:** -If applicable, add screenshots to help explain your problem. +Describe what the expected behavior or outcome should have been in the absence of the incident. -**Additional context** +**Current Impact:** -Add any other context about the problem here. +Explain the current impact of the incident on the project or users. +Include any errors, downtime, or loss of functionality experienced. + +**Resolution Steps Taken (if any):** + +If any steps have been taken to resolve the incident or mitigate its impact, describe them here. +This can include any temporary fixes, workarounds, or ongoing efforts to address the issue. + +**Additional Information:** + +Add any additional information that you think might be helpful for understanding or addressing the incident. +Include relevant logs, error messages, or any other supporting details. -- GitLab