# How to reopen issue in ansible (github)

**URL:** <https://forum.ansible.com/t/how-to-reopen-issue-in-ansible-github/28963>\
**Category:** Ansible Project\
**Created:** [November 7, 2018, 12:28pm UTC](https://forum.ansible.com/t/how-to-reopen-issue-in-ansible-github/28963 "2018-11-07T12:28:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![profhase85](https://avatars.discourse-cdn.com/v4/letter/p/2bfe46/32.png) [@profhase85](https://forum.ansible.com/u/profhase85)\
**Post date:** [November 7, 2018, 12:28pm UTC](https://forum.ansible.com/t/how-to-reopen-issue-in-ansible-github/28963/1 "2018-11-07T12:28:51Z")

</div>

Hi @all,

could someone please tell me and/or reopen the following issue:

[https://github.com/ansible/ansible/issues/25046](https://github.com/ansible/ansible/issues/25046)

The issue is closed and is supposed to be fixed for 2.3 , it still exists in 2.6, though

Thanks a lot

---

<div class="post-metadata">

**Author:** ![tkuratom](https://avatars.discourse-cdn.com/v4/letter/t/b19c9b/32.png) [@tkuratom](https://forum.ansible.com/u/tkuratom)\
**Post date:** [November 7, 2018, 3:15pm UTC](https://forum.ansible.com/t/how-to-reopen-issue-in-ansible-github/28963/2 "2018-11-07T15:15:48Z")

</div>

Open a new issue. If you think it is related to the old issue, link to the old issue in the new one.

Since that issue says that the issue was fixed, testing with the version containing the fix could tell us if there was a regression versus a new and unrelated problem.