debian-mirror-gitlab/.gitlab/issue_templates/Bug.md

86 lines
2.4 KiB
Markdown
Raw Normal View History

2019-05-05 18:10:48 +05:30
<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
2021-12-11 22:18:48 +05:30
filtered by the "regression" or "type::bug" label:
2019-05-05 18:10:48 +05:30
2019-12-21 20:55:43 +05:30
- https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression
2021-12-11 22:18:48 +05:30
- https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug
2019-05-05 18:10:48 +05:30
and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
2020-11-24 15:15:51 +05:30
<!-- Summarize the bug encountered concisely. -->
2019-05-05 18:10:48 +05:30
### Steps to reproduce
2020-11-24 15:15:51 +05:30
<!-- Describe how one can reproduce the issue - this is very important. Please use an ordered list. -->
2019-05-05 18:10:48 +05:30
### Example Project
2020-11-24 15:15:51 +05:30
<!-- 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
will also determine whether the bug is fixed in a more recent version. -->
2019-05-05 18:10:48 +05:30
### What is the current *bug* behavior?
2020-11-24 15:15:51 +05:30
<!-- Describe what actually happens. -->
2019-05-05 18:10:48 +05:30
### What is the expected *correct* behavior?
2020-11-24 15:15:51 +05:30
<!-- Describe what you should see instead. -->
2019-05-05 18:10:48 +05:30
### Relevant logs and/or screenshots
2020-11-24 15:15:51 +05:30
<!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code
as it's tough to read otherwise. -->
2019-05-05 18:10:48 +05:30
### Output of checks
2020-11-24 15:15:51 +05:30
<!-- If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com -->
2019-05-05 18:10:48 +05:30
#### Results of GitLab environment info
2020-11-24 15:15:51 +05:30
<!-- Input any relevant GitLab environment information if needed. -->
2019-05-05 18:10:48 +05:30
<details>
<summary>Expand for output related to GitLab environment info</summary>
2020-04-22 19:07:51 +05:30
2019-05-05 18:10:48 +05:30
<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
2020-11-24 15:15:51 +05:30
<!-- Input any relevant GitLab application check information if needed. -->
2019-05-05 18:10:48 +05:30
<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
2020-11-24 15:15:51 +05:30
<!-- If you can, link to the line of code that might be responsible for the problem. -->
2019-05-05 18:10:48 +05:30
2021-12-11 22:18:48 +05:30
/label ~"type::bug"