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've 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 isn't 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?

```
(Paste verbatim command output here)
```
Moving the github issue template file to this repo 2014-09-09 17:59:39 +02:00			`##### Issue Type:`

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. 2016-02-18 04:23:40 +01:00			`Please pick one and delete the rest:`
			`- Bug Report`
			`- Feature Idea`
			`- Documentation Report`
Moving the github issue template file to this repo 2014-09-09 17:59:39 +02:00
			`##### Ansible Version:`

Use triple-backticks for verbatim output It's easier than indenting by four spaces, as @willthames points out. 2016-02-18 11:41:47 +01:00			```
			`(Paste verbatim output from “ansible --version” here)`
			```
Moving the github issue template file to this repo 2014-09-09 17:59:39 +02:00
Config might be important for issues. 2015-05-08 00:24:33 +02:00			`##### Ansible Configuration:`

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. 2016-02-18 04:23:40 +01:00			`Please mention any settings you've changed/added/removed in ansible.cfg`
			`(or using the ANSIBLE_* environment variables).`
Config might be important for issues. 2015-05-08 00:24:33 +02:00
Moving the github issue template file to this repo 2014-09-09 17:59:39 +02:00			`##### Environment:`

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. 2016-02-18 04:23:40 +01:00			`Please mention the OS you are running Ansible from, and the OS you are`
			`managing, or say “N/A” for anything that isn't platform-specific.`
Moving the github issue template file to this repo 2014-09-09 17:59:39 +02:00
			`##### Summary:`

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. 2016-02-18 04:23:40 +01:00			`Please explain the problem briefly.`
Moving the github issue template file to this repo 2014-09-09 17:59:39 +02:00
			`##### Steps To Reproduce:`

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. 2016-02-18 04:23:40 +01:00			`For bugs, please show exactly how to reproduce the problem. For new`
			`features, show how the feature would be used.`

Use triple-backticks for verbatim output It's easier than indenting by four spaces, as @willthames points out. 2016-02-18 11:41:47 +01:00			```
			`(Paste example playbooks or commands here)`
			```

			`You can also paste gist.github.com links for larger files.`
Moving the github issue template file to this repo 2014-09-09 17:59:39 +02:00
			`##### Expected Results:`

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. 2016-02-18 04:23:40 +01:00			`What did you expect to happen when running the steps above?`
Moving the github issue template file to this repo 2014-09-09 17:59:39 +02:00
			`##### Actual Results:`

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. 2016-02-18 04:23:40 +01:00			`What actually happened?`
Moving the github issue template file to this repo 2014-09-09 17:59:39 +02:00
Use triple-backticks for verbatim output It's easier than indenting by four spaces, as @willthames points out. 2016-02-18 11:41:47 +01:00			```
			`(Paste verbatim command output here)`
			```