# Ansibot issue with resolved\_by\_pr tag

**URL:** <https://forum.ansible.com/t/ansibot-issue-with-resolved-by-pr-tag/22567>\
**Category:** Ansible Developer\
**Created:** [September 16, 2016, 1:51pm UTC](https://forum.ansible.com/t/ansibot-issue-with-resolved-by-pr-tag/22567 "2016-09-16T13:51:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rob\_White](https://avatars.discourse-cdn.com/v4/letter/r/71c47a/32.png) [@Rob\_White](https://forum.ansible.com/u/Rob_White)\
**Post date:** [September 16, 2016, 1:51pm UTC](https://forum.ansible.com/t/ansibot-issue-with-resolved-by-pr-tag/22567/1 "2016-09-16T13:51:18Z")

</div>

Can we change the resolved\_by\_pr label to not close the issue if the PR hasn’t been merged yet?

I don’t think the bot should close the ticket just in case the PR isn’t merged for one reason or another and the issue still exists.

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [September 17, 2016, 4:09pm UTC](https://forum.ansible.com/t/ansibot-issue-with-resolved-by-pr-tag/22567/2 "2016-09-17T16:09:45Z")

</div>

Hi Rob,  
Good idea, seems like this is already on the list of things to do [issuetriage: resolved\_by\_pr should check that the PR was merged before closing issue · Issue #129 · ansible/ansibullbot · GitHub](https://github.com/ansible/ansibullbot/issues/129)

Feel free to subscribe to that ticket for updates.

Kind regards,  
John Barker