Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
N
NTRfC
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
TFD - Institut für Turbomaschinen und Fluid-Dynamik
tools
NTRfC
Commits
40ebe14c
Commit
40ebe14c
authored
1 year ago
by
many
Browse files
Options
Downloads
Patches
Plain Diff
incidence template
parent
8c9d7e81
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
.gitlab/issue_templates/incidence_template.md
+23
-13
23 additions, 13 deletions
.gitlab/issue_templates/incidence_template.md
with
23 additions
and
13 deletions
.gitlab/issue_templates/incidence_template.md
+
23
−
13
View file @
40ebe14c
**
Describe the incident
**
**
Summary:
**
A clear and concise description of what the problem is
.
Provide a brief summary of the incident
.
**Descri
be step by step the course of the event
**
**Descri
ption:
**
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.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment