# Whether to reopen issue.

**URL:** <https://forum.ansible.com/t/whether-to-reopen-issue/16439>\
**Category:** Ansible Project\
**Created:** [October 6, 2014, 11:05am UTC](https://forum.ansible.com/t/whether-to-reopen-issue/16439 "2014-10-06T11:05:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joseph\_Price](https://avatars.discourse-cdn.com/v4/letter/j/e274bd/32.png) [@Joseph\_Price](https://forum.ansible.com/u/Joseph_Price)\
**Post date:** [October 6, 2014, 11:05am UTC](https://forum.ansible.com/t/whether-to-reopen-issue/16439/1 "2014-10-06T11:05:03Z")

</div>

Howdy!

I opened an issue for a behaviour change between 1.7.1 & 1.7.2: [https://github.com/ansible/ansible/issues/9171](https://github.com/ansible/ansible/issues/9171)

I’m pretty sure it’s fixed in devel though I seem to have confused myself with git bisect trying to figure out why.

My question is whether you would like this issue reopened in [https://github.com/ansible/ansible-modules-core](https://github.com/ansible/ansible-modules-core) to track it? Although I believe it’s fixed in devel, I would rather like to see a 1.7.3 release restoring the previous behaviour.

Thanks for your time,  
Joe

---

<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:** [October 6, 2014, 12:31pm UTC](https://forum.ansible.com/t/whether-to-reopen-issue/16439/2 "2014-10-06T12:31:46Z")

</div>

It’s uncertain if we are going to cut a 1.7.3 release at this time.

When/if we do, we typically backport issues from the devel branch that make sense.