# Bug reporting fixing ettiquette. Bug before fix?

**URL:** <https://forum.ansible.com/t/bug-reporting-fixing-ettiquette-bug-before-fix/16194>\
**Category:** Ansible Project\
**Created:** [September 12, 2014, 11:09am UTC](https://forum.ansible.com/t/bug-reporting-fixing-ettiquette-bug-before-fix/16194 "2014-09-12T11:09:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stephen\_Gargan](https://avatars.discourse-cdn.com/v4/letter/s/c67d28/32.png) [@Stephen\_Gargan](https://forum.ansible.com/u/Stephen_Gargan)\
**Post date:** [September 12, 2014, 11:09am UTC](https://forum.ansible.com/t/bug-reporting-fixing-ettiquette-bug-before-fix/16194/1 "2014-09-12T11:09:47Z")

</div>

Hit an issue with overriding include parameters with variables passed in as extras. I’ve made a fix and added a pull request, [https://github.com/ansible/ansible/pull/8984](https://github.com/ansible/ansible/pull/8984)

Added it as a bugfix pull request, but wasn’t sure if there should have been a bug report first. What is the done thing? Is it ok to post a fix without a bug or does this break your bot reporting? Might it result in poor prioritization of the issue?

Thanks,

Steve.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [September 12, 2014, 1:57pm UTC](https://forum.ansible.com/t/bug-reporting-fixing-ettiquette-bug-before-fix/16194/2 "2014-09-12T13:57:45Z")

</div>

Yeah, I’d much rather just have the bugfix\_pr submitted directly rather than have two tickets in the system.

GitHub is great because there’s a fantastic and ginormous group of people there, but the ticket management system and search is not so great, so having less tickets to search through is better in the long run 🙂

Thanks very much for submitting the fix!