# Searching issues with module name

**URL:** <https://discuss.python.org/t/searching-issues-with-module-name/15846>\
**Category:** Core Development\
**Created:** [May 19, 2022, 5:54am UTC](https://discuss.python.org/t/searching-issues-with-module-name/15846 "2022-05-19T05:54:00Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ezio-melotti](https://avatars.discourse-cdn.com/v4/letter/e/f17d59/32.png) [@ezio-melotti](https://discuss.python.org/u/ezio-melotti)\
**Post date:** [May 19, 2022, 6:17am UTC](https://discuss.python.org/t/searching-issues-with-module-name/15846/2 "2022-05-19T06:17:52Z")

</div>

There are a few options, depending on the goals:

- You can already use [`in:title json`](https://github.com/python/cpython/issues?q=is%3Aopen+in%3Atitle+json) to narrow down the search:
  - it doesn’t find all the issues and include false positives

- You can add “[json]” in the title and use the search query above:
  - triages might not know to add `[json]` in the title
  - GitHub search seems to ignore the `[]`

- We can add a label:
  - it’s easier for filtering and for triagers to add
  - it’s useful to notify people subscribed to the label
  - if we do it should be called `expert-json`\[1\]

- You can [create a project](https://discuss.python.org/t/using-github-beta-projects-in-our-workflow/15090) to track issues:
  - you will have to add existing issues manually
  - you have more freedom in organizing them
  - triagers might not know to add new json issues to the project

Adding the label is probably the easiest solution\[2\], unless the other solutions are enough to solve your problem. Let me know if you want me to add it.

* * *

1. `stdlib`, `docs`, `tests`, `interpreter-core`, `extension-modules` are in a group on their own. 

2. we recently added `expert-sqlite` to solve the same problem

---

_[View the full topic](https://discuss.python.org/t/searching-issues-with-module-name/15846)._