gitlab-org--gitlab-foss/.gitlab/issue_templates/Bug.md

### Summary

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Expected behavior

(What you should see instead)

### Actual behavior

(What actually happens)

### 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 application Check

(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)

#### Results of GitLab environment info

(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`)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)
Link to the issue templates in Contributing guide Change to use a better title style Add backticks to code segments Spelling and Grammar 2016-08-25 10:41:51 -04:00			`### Summary`
First pass for community issue templates * Include "Bug" template from the contribution guide * Include "Feature Proposal" template from the contribution guide 2016-08-23 06:28:11 -04:00
Reflect template addition in the contributing guide Adjust bug template to adhere to standard bug report format * https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines * Guidelines use the following format - Summary - Steps to Reproduce - Expected Behaviour - Actual Behaviour 2016-08-24 09:56:32 -04:00			`(Summarize the bug encountered concisely)`
First pass for community issue templates * Include "Bug" template from the contribution guide * Include "Feature Proposal" template from the contribution guide 2016-08-23 06:28:11 -04:00
Link to the issue templates in Contributing guide Change to use a better title style Add backticks to code segments Spelling and Grammar 2016-08-25 10:41:51 -04:00			`### Steps to reproduce`
First pass for community issue templates * Include "Bug" template from the contribution guide * Include "Feature Proposal" template from the contribution guide 2016-08-23 06:28:11 -04:00
			`(How one can reproduce the issue - this is very important)`

Link to the issue templates in Contributing guide Change to use a better title style Add backticks to code segments Spelling and Grammar 2016-08-25 10:41:51 -04:00			`### Expected behavior`
First pass for community issue templates * Include "Bug" template from the contribution guide * Include "Feature Proposal" template from the contribution guide 2016-08-23 06:28:11 -04:00
			`(What you should see instead)`

Rename behaviour to behavior in bug issue template for consistency 2016-09-01 23:01:02 -04:00			`### Actual behavior`
Reflect template addition in the contributing guide Adjust bug template to adhere to standard bug report format * https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines * Guidelines use the following format - Summary - Steps to Reproduce - Expected Behaviour - Actual Behaviour 2016-08-24 09:56:32 -04:00
			`(What actually happens)`

Link to the issue templates in Contributing guide Change to use a better title style Add backticks to code segments Spelling and Grammar 2016-08-25 10:41:51 -04:00			`### Relevant logs and/or screenshots`
First pass for community issue templates * Include "Bug" template from the contribution guide * Include "Feature Proposal" template from the contribution guide 2016-08-23 06:28:11 -04:00
			(Paste any relevant logs - please use code blocks (```) to format console output,
			`logs, and code as it's very hard to read otherwise.)`

Link to the issue templates in Contributing guide Change to use a better title style Add backticks to code segments Spelling and Grammar 2016-08-25 10:41:51 -04:00			`### Output of checks`
First pass for community issue templates * Include "Bug" template from the contribution guide * Include "Feature Proposal" template from the contribution guide 2016-08-23 06:28:11 -04:00
Encourage bug reporters to mention if they use GitLab.com [ci skip] 2016-12-06 11:08:53 -05:00			`(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)`

Link to the issue templates in Contributing guide Change to use a better title style Add backticks to code segments Spelling and Grammar 2016-08-25 10:41:51 -04:00			`#### Results of GitLab application Check`
First pass for community issue templates * Include "Bug" template from the contribution guide * Include "Feature Proposal" template from the contribution guide 2016-08-23 06:28:11 -04:00
			`(For installations with omnibus-gitlab package run and paste the output of:`
Link to the issue templates in Contributing guide Change to use a better title style Add backticks to code segments Spelling and Grammar 2016-08-25 10:41:51 -04:00			`sudo gitlab-rake gitlab:check SANITIZE=true`)
First pass for community issue templates * Include "Bug" template from the contribution guide * Include "Feature Proposal" template from the contribution guide 2016-08-23 06:28:11 -04:00
			`(For installations from source run and paste the output of:`
Link to the issue templates in Contributing guide Change to use a better title style Add backticks to code segments Spelling and Grammar 2016-08-25 10:41:51 -04:00			`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`)
First pass for community issue templates * Include "Bug" template from the contribution guide * Include "Feature Proposal" template from the contribution guide 2016-08-23 06:28:11 -04:00
			`(we will only investigate if the tests are passing)`

Link to the issue templates in Contributing guide Change to use a better title style Add backticks to code segments Spelling and Grammar 2016-08-25 10:41:51 -04:00			`#### Results of GitLab environment info`
First pass for community issue templates * Include "Bug" template from the contribution guide * Include "Feature Proposal" template from the contribution guide 2016-08-23 06:28:11 -04:00
			`(For installations with omnibus-gitlab package run and paste the output of:`
Link to the issue templates in Contributing guide Change to use a better title style Add backticks to code segments Spelling and Grammar 2016-08-25 10:41:51 -04:00			`sudo gitlab-rake gitlab:env:info`)
First pass for community issue templates * Include "Bug" template from the contribution guide * Include "Feature Proposal" template from the contribution guide 2016-08-23 06:28:11 -04:00
			`(For installations from source run and paste the output of:`
Link to the issue templates in Contributing guide Change to use a better title style Add backticks to code segments Spelling and Grammar 2016-08-25 10:41:51 -04:00			`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
First pass for community issue templates * Include "Bug" template from the contribution guide * Include "Feature Proposal" template from the contribution guide 2016-08-23 06:28:11 -04:00
Link to the issue templates in Contributing guide Change to use a better title style Add backticks to code segments Spelling and Grammar 2016-08-25 10:41:51 -04:00			`### Possible fixes`
First pass for community issue templates * Include "Bug" template from the contribution guide * Include "Feature Proposal" template from the contribution guide 2016-08-23 06:28:11 -04:00
			`(If you can, link to the line of code that might be responsible for the problem)`