ef4c776bd3
The issue template for bugs has a notice at the start that mentions to search for duplicates before creating a new issue. Then the reporter is asked to remove the notice once read, presumptively to avoid noise in the actual issue. Instead of that, we can make that part of the issue template an html comment, so it won't be rendered in the final result. This avoids the tedious task of removing that part of the notice. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/43580
87 lines
2.4 KiB
Markdown
87 lines
2.4 KiB
Markdown
<!---
|
|
Please read this!
|
|
|
|
Before opening a new issue, make sure to search for keywords in the issues
|
|
filtered by the "regression" or "bug" label.
|
|
|
|
For the Community Edition issue tracker:
|
|
|
|
- https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=regression
|
|
- https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=bug
|
|
|
|
For the Enterprise Edition issue tracker:
|
|
|
|
- https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=regression
|
|
- https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=bug
|
|
|
|
and verify the issue you're about to submit isn't a duplicate.
|
|
--->
|
|
|
|
### Summary
|
|
|
|
(Summarize the bug encountered concisely)
|
|
|
|
### Steps to reproduce
|
|
|
|
(How one can reproduce the issue - this is very important)
|
|
|
|
### Example Project
|
|
|
|
(If possible, please create an example project here on GitLab.com that exhibits the problematic behaviour, and link to it here in the bug report)
|
|
|
|
(If you are using an older version of GitLab, this will also determine whether the bug has been fixed in a more recent version)
|
|
|
|
### What is the current *bug* behavior?
|
|
|
|
(What actually happens)
|
|
|
|
### What is the expected *correct* behavior?
|
|
|
|
(What you should see instead)
|
|
|
|
### Relevant logs and/or screenshots
|
|
|
|
(Paste any relevant logs - please use code blocks (```) to format console output,
|
|
logs, and code as it's very hard to read otherwise.)
|
|
|
|
### Output of checks
|
|
|
|
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
|
|
|
|
#### Results of GitLab environment info
|
|
|
|
<details>
|
|
<summary>Expand for output related to GitLab environment info</summary>
|
|
<pre>
|
|
|
|
(For installations with omnibus-gitlab package run and paste the output of:
|
|
`sudo gitlab-rake gitlab:env:info`)
|
|
|
|
(For installations from source run and paste the output of:
|
|
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
|
|
|
|
</pre>
|
|
</details>
|
|
|
|
#### Results of GitLab application Check
|
|
|
|
<details>
|
|
<summary>Expand for output related to the GitLab application check</summary>
|
|
<pre>
|
|
|
|
(For installations with omnibus-gitlab package run and paste the output of:
|
|
`sudo gitlab-rake gitlab:check SANITIZE=true`)
|
|
|
|
(For installations from source run and paste the output of:
|
|
`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`)
|
|
|
|
(we will only investigate if the tests are passing)
|
|
|
|
</pre>
|
|
</details>
|
|
|
|
### Possible fixes
|
|
|
|
(If you can, link to the line of code that might be responsible for the problem)
|
|
|
|
/label ~bug
|