Commit fa1c3375 authored by Lin Jen-Shin's avatar Lin Jen-Shin

Merge branch 'dimitrieh-master-patch-44780' into 'master'

Update the bug issue template to be more efficient

See merge request gitlab-org/gitlab!40519
parents ad4d7712 cbf9020d
...@@ -12,37 +12,39 @@ and verify the issue you're about to submit isn't a duplicate. ...@@ -12,37 +12,39 @@ and verify the issue you're about to submit isn't a duplicate.
### Summary ### Summary
(Summarize the bug encountered concisely) <!-- Summarize the bug encountered concisely. -->
### Steps to reproduce ### Steps to reproduce
(How one can reproduce the issue - this is very important) <!-- Describe how one can reproduce the issue - this is very important. Please use an ordered list. -->
### Example Project ### Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report) <!-- If possible, please create an example project here on GitLab.com that exhibits the problematic
behavior, and link to it here in the bug report. If you are using an older version of GitLab, this
(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version) will also determine whether the bug is fixed in a more recent version. -->
### What is the current *bug* behavior? ### What is the current *bug* behavior?
(What actually happens) <!-- Describe what actually happens. -->
### What is the expected *correct* behavior? ### What is the expected *correct* behavior?
(What you should see instead) <!-- Describe what you should see instead. -->
### Relevant logs and/or screenshots ### Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, <!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code
logs, and code as it's tough to read otherwise.) as it's tough to read otherwise. -->
### Output of checks ### Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com) <!-- If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com -->
#### Results of GitLab environment info #### Results of GitLab environment info
<!-- Input any relevant GitLab environment information if needed. -->
<details> <details>
<summary>Expand for output related to GitLab environment info</summary> <summary>Expand for output related to GitLab environment info</summary>
...@@ -59,6 +61,8 @@ logs, and code as it's tough to read otherwise.) ...@@ -59,6 +61,8 @@ logs, and code as it's tough to read otherwise.)
#### Results of GitLab application Check #### Results of GitLab application Check
<!-- Input any relevant GitLab application check information if needed. -->
<details> <details>
<summary>Expand for output related to the GitLab application check</summary> <summary>Expand for output related to the GitLab application check</summary>
<pre> <pre>
...@@ -76,6 +80,6 @@ logs, and code as it's tough to read otherwise.) ...@@ -76,6 +80,6 @@ logs, and code as it's tough to read otherwise.)
### Possible fixes ### Possible fixes
(If you can, link to the line of code that might be responsible for the problem) <!-- If you can, link to the line of code that might be responsible for the problem. -->
/label ~bug /label ~bug
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment