# Should we have issue templates?

**URL:** <https://forum.ansible.com/t/should-we-have-issue-templates/1039>\
**Category:** Forum Guide & Feedback\
**Tags:** feedback-wanted, forum-issue\
**Created:** [September 22, 2023, 9:50am UTC](https://forum.ansible.com/t/should-we-have-issue-templates/1039 "2023-09-22T09:50:27Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![gwmngilfen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gwmngilfen/32/6_2.png) [@gwmngilfen](https://forum.ansible.com/u/gwmngilfen)\
**Post date:** [September 27, 2023, 9:17am UTC](https://forum.ansible.com/t/should-we-have-issue-templates/1039/14 "2023-09-27T09:17:05Z")

</div>

OK, so I think we need to get this going. How does the following template sound?

* * *

**Please replace this text with a description of your issue**. You should:

- Include the version(s) of the relevant software tools, libraries, collections etc
- Include relavant logs from the issue
- Use backticks (```) to help format your logs and code (easy-to-read posts are easier to answer too!), like this:

```auto
- my code!

```

- Set at least one tag (the experts follow the tags, so the right people will find you if you tag)

* * *

I’m deliberately _not_ mentioning the over-use of Groups, and emphasising tag use instead - drawing attention to the possibility of mentioning a Group might actually _increase_ the use of it. I think we should use [replies like this](http://forum.ansible.com/t/cant-run-ssh-against-an-network-device-extreme-slx-switch/1137/2) when we see people abusing the feature 🙂

How does that sound?

---

_[View the full topic](https://forum.ansible.com/t/should-we-have-issue-templates/1039)._