ansible/ISSUE_TEMPLATE.md

##### Issue Type:

<!--- Please pick one and delete the rest: -->
 - Bug Report
 - Feature Idea
 - Documentation Report

##### Ansible Version:

```
<!--- Paste verbatim output from “ansible --version” here -->
```

##### Ansible Configuration:

<!---
Please mention any settings you have changed/added/removed in ansible.cfg
(or using the ANSIBLE_* environment variables).
-->

##### Environment:

<!---
Please mention the OS you are running Ansible from, and the OS you are
managing, or say “N/A” for anything that is not platform-specific.
-->

##### Summary:

<!--- Please explain the problem briefly -->

##### Steps To Reproduce:

<!---
For bugs, please show exactly how to reproduce the problem. For new
features, show how the feature would be used.
-->

```
<!--- Paste example playbooks or commands here -->
```

<!--- You can also paste gist.github.com links for larger files -->

##### Expected Results:

<!--- What did you expect to happen when running the steps above? -->

##### Actual Results:

<!--- What actually happened? If possible run with high verbosity (-vvvv) -->

```
<!--- Paste verbatim command output here -->
```
Moving the github issue template file to this repo 10 years ago			`##### Issue Type:`

Put the advice to the user as comments in the template Most issues include parts of the advice from the template, which adds noise to tickets. E.g. A lot of tickets include the text "Please pick one and delete the rest:" By adding the advice to the user as comments (<!--- comment -->) we achieve two important things: 1. The advice does not end up in the actual issue ticket or pull request 2. It is easier for the user to differentiate its own input and the original advice (And my help them to clean up the advice as well, which in fact is now no longer necessary) 9 years ago			`<!--- Please pick one and delete the rest: -->`
Edit the ISSUE_TEMPLATE The old template was effusive at the expense of making the text harder to read and easier to miss things in. This one is more direct, and easy to scan quickly. 9 years ago			`- Bug Report`
			`- Feature Idea`
			`- Documentation Report`
Moving the github issue template file to this repo 10 years ago
			`##### Ansible Version:`

Use triple-backticks for verbatim output It's easier than indenting by four spaces, as @willthames points out. 9 years ago			```
Put the advice to the user as comments in the template Most issues include parts of the advice from the template, which adds noise to tickets. E.g. A lot of tickets include the text "Please pick one and delete the rest:" By adding the advice to the user as comments (<!--- comment -->) we achieve two important things: 1. The advice does not end up in the actual issue ticket or pull request 2. It is easier for the user to differentiate its own input and the original advice (And my help them to clean up the advice as well, which in fact is now no longer necessary) 9 years ago			`<!--- Paste verbatim output from “ansible --version” here -->`
Use triple-backticks for verbatim output It's easier than indenting by four spaces, as @willthames points out. 9 years ago			```
Moving the github issue template file to this repo 10 years ago
Config might be important for issues. 10 years ago			`##### Ansible Configuration:`

Put the advice to the user as comments in the template Most issues include parts of the advice from the template, which adds noise to tickets. E.g. A lot of tickets include the text "Please pick one and delete the rest:" By adding the advice to the user as comments (<!--- comment -->) we achieve two important things: 1. The advice does not end up in the actual issue ticket or pull request 2. It is easier for the user to differentiate its own input and the original advice (And my help them to clean up the advice as well, which in fact is now no longer necessary) 9 years ago			`<!---`
			`Please mention any settings you have changed/added/removed in ansible.cfg`
Edit the ISSUE_TEMPLATE The old template was effusive at the expense of making the text harder to read and easier to miss things in. This one is more direct, and easy to scan quickly. 9 years ago			`(or using the ANSIBLE_* environment variables).`
Put the advice to the user as comments in the template Most issues include parts of the advice from the template, which adds noise to tickets. E.g. A lot of tickets include the text "Please pick one and delete the rest:" By adding the advice to the user as comments (<!--- comment -->) we achieve two important things: 1. The advice does not end up in the actual issue ticket or pull request 2. It is easier for the user to differentiate its own input and the original advice (And my help them to clean up the advice as well, which in fact is now no longer necessary) 9 years ago			`-->`
Config might be important for issues. 10 years ago
Moving the github issue template file to this repo 10 years ago			`##### Environment:`

Put the advice to the user as comments in the template Most issues include parts of the advice from the template, which adds noise to tickets. E.g. A lot of tickets include the text "Please pick one and delete the rest:" By adding the advice to the user as comments (<!--- comment -->) we achieve two important things: 1. The advice does not end up in the actual issue ticket or pull request 2. It is easier for the user to differentiate its own input and the original advice (And my help them to clean up the advice as well, which in fact is now no longer necessary) 9 years ago			`<!---`
Edit the ISSUE_TEMPLATE The old template was effusive at the expense of making the text harder to read and easier to miss things in. This one is more direct, and easy to scan quickly. 9 years ago			`Please mention the OS you are running Ansible from, and the OS you are`
Put the advice to the user as comments in the template Most issues include parts of the advice from the template, which adds noise to tickets. E.g. A lot of tickets include the text "Please pick one and delete the rest:" By adding the advice to the user as comments (<!--- comment -->) we achieve two important things: 1. The advice does not end up in the actual issue ticket or pull request 2. It is easier for the user to differentiate its own input and the original advice (And my help them to clean up the advice as well, which in fact is now no longer necessary) 9 years ago			`managing, or say “N/A” for anything that is not platform-specific.`
			`-->`
Moving the github issue template file to this repo 10 years ago
			`##### Summary:`

Put the advice to the user as comments in the template Most issues include parts of the advice from the template, which adds noise to tickets. E.g. A lot of tickets include the text "Please pick one and delete the rest:" By adding the advice to the user as comments (<!--- comment -->) we achieve two important things: 1. The advice does not end up in the actual issue ticket or pull request 2. It is easier for the user to differentiate its own input and the original advice (And my help them to clean up the advice as well, which in fact is now no longer necessary) 9 years ago			`<!--- Please explain the problem briefly -->`
Moving the github issue template file to this repo 10 years ago
			`##### Steps To Reproduce:`

Put the advice to the user as comments in the template Most issues include parts of the advice from the template, which adds noise to tickets. E.g. A lot of tickets include the text "Please pick one and delete the rest:" By adding the advice to the user as comments (<!--- comment -->) we achieve two important things: 1. The advice does not end up in the actual issue ticket or pull request 2. It is easier for the user to differentiate its own input and the original advice (And my help them to clean up the advice as well, which in fact is now no longer necessary) 9 years ago			`<!---`
Edit the ISSUE_TEMPLATE The old template was effusive at the expense of making the text harder to read and easier to miss things in. This one is more direct, and easy to scan quickly. 9 years ago			`For bugs, please show exactly how to reproduce the problem. For new`
			`features, show how the feature would be used.`
Put the advice to the user as comments in the template Most issues include parts of the advice from the template, which adds noise to tickets. E.g. A lot of tickets include the text "Please pick one and delete the rest:" By adding the advice to the user as comments (<!--- comment -->) we achieve two important things: 1. The advice does not end up in the actual issue ticket or pull request 2. It is easier for the user to differentiate its own input and the original advice (And my help them to clean up the advice as well, which in fact is now no longer necessary) 9 years ago			`-->`
Edit the ISSUE_TEMPLATE The old template was effusive at the expense of making the text harder to read and easier to miss things in. This one is more direct, and easy to scan quickly. 9 years ago
Use triple-backticks for verbatim output It's easier than indenting by four spaces, as @willthames points out. 9 years ago			```
Put the advice to the user as comments in the template Most issues include parts of the advice from the template, which adds noise to tickets. E.g. A lot of tickets include the text "Please pick one and delete the rest:" By adding the advice to the user as comments (<!--- comment -->) we achieve two important things: 1. The advice does not end up in the actual issue ticket or pull request 2. It is easier for the user to differentiate its own input and the original advice (And my help them to clean up the advice as well, which in fact is now no longer necessary) 9 years ago			`<!--- Paste example playbooks or commands here -->`
Use triple-backticks for verbatim output It's easier than indenting by four spaces, as @willthames points out. 9 years ago			```

Put the advice to the user as comments in the template Most issues include parts of the advice from the template, which adds noise to tickets. E.g. A lot of tickets include the text "Please pick one and delete the rest:" By adding the advice to the user as comments (<!--- comment -->) we achieve two important things: 1. The advice does not end up in the actual issue ticket or pull request 2. It is easier for the user to differentiate its own input and the original advice (And my help them to clean up the advice as well, which in fact is now no longer necessary) 9 years ago			`<!--- You can also paste gist.github.com links for larger files -->`
Moving the github issue template file to this repo 10 years ago
			`##### Expected Results:`

Put the advice to the user as comments in the template Most issues include parts of the advice from the template, which adds noise to tickets. E.g. A lot of tickets include the text "Please pick one and delete the rest:" By adding the advice to the user as comments (<!--- comment -->) we achieve two important things: 1. The advice does not end up in the actual issue ticket or pull request 2. It is easier for the user to differentiate its own input and the original advice (And my help them to clean up the advice as well, which in fact is now no longer necessary) 9 years ago			`<!--- What did you expect to happen when running the steps above? -->`
Moving the github issue template file to this repo 10 years ago
			`##### Actual Results:`

added note for verbosity 9 years ago			`<!--- What actually happened? If possible run with high verbosity (-vvvv) -->`
Moving the github issue template file to this repo 10 years ago
Use triple-backticks for verbatim output It's easier than indenting by four spaces, as @willthames points out. 9 years ago			```
Put the advice to the user as comments in the template Most issues include parts of the advice from the template, which adds noise to tickets. E.g. A lot of tickets include the text "Please pick one and delete the rest:" By adding the advice to the user as comments (<!--- comment -->) we achieve two important things: 1. The advice does not end up in the actual issue ticket or pull request 2. It is easier for the user to differentiate its own input and the original advice (And my help them to clean up the advice as well, which in fact is now no longer necessary) 9 years ago			`<!--- Paste verbatim command output here -->`
Use triple-backticks for verbatim output It's easier than indenting by four spaces, as @willthames points out. 9 years ago			```