# Finding issues without a pull request to work on

**URL:** <https://discuss.python.org/t/finding-issues-without-a-pull-request-to-work-on/103554>\
**Category:** Core Development\
**Created:** [September 5, 2025, 3:38am UTC](https://discuss.python.org/t/finding-issues-without-a-pull-request-to-work-on/103554 "2025-09-05T03:38:18Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![encukou](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/encukou/32/2461_2.png) [@encukou](https://discuss.python.org/u/encukou)\
**Post date:** [September 5, 2025, 9:24am UTC](https://discuss.python.org/t/finding-issues-without-a-pull-request-to-work-on/103554/10 "2025-09-05T09:24:16Z")

</div>

> [@hugovk](#):
>
> Right now, we have 376 open issues with their linked PRs merged or closed. Some of these are intentionally left open because they need future work.

Would a `dont-close-yet` or `more-work-pending` label be a good idea, to keep those out of dashboards?

---

_[View the full topic](https://discuss.python.org/t/finding-issues-without-a-pull-request-to-work-on/103554)._