In #803 we've added information to explain why some modules cannot be disabled when fields provided by these modules are in use in certain content types. This is a big UX+, but...
The "Required by: Field type(s) in use..." seems a bit "cryptic" to me and the "...see Field list" link that follows leads to a list of all fields instead of a filtered list of only the fields provided by the specific module. This feature can be further improved in various ways:
1. Instead of the generic "Required by: Field type(s) in use...", we could be more specific and have it for example like so: "Required by the Tags field used in the Article content type".
2. The part of this text that is the actual name(s) of the content type(s) would be links to the respective content type field edit page. Same as the links in the "Used in" column at the "Field list" page (/admin/reports/fields).
This way, an admin seeking to disable certain modules will not have to continuously hop from the modules list to the fields list and finally to the specific content types that hold the fields in question and then back to the modules list.
Related: #849
Recent comments
Let's consolidate this with https://forum.backdropcms.org/forum/weekly-dev-meetings-focus-top-wish-list-items-start-march-26-2026
Backdrop CMS Core Priorities
This is a really good idea. I nearly always search on GitHub if I'm not sure of the name. That said, there is still room for improvement in GitHub as many repos have a useless description...
Weekly dev meetings to focus on top wish list items start March 26, 2026.
I'd suggest module search to get discussed as a possible top priority. Our module search page on backdropcms.org doesn't do a good job. Neither does the module search on admin/...
Weekly dev meetings to focus on top wish list items start March 26, 2026.