A lot of projects use bots to handle issues. For example, if an issue is open for a long time with no update, then a bot will add a comment: “Is this problem still valid?”. If no answer comes, then it can be marked stale with a label, and can be closed after some more time.
Of course this is just one part.
The other part is that a bug triage team is needed who make sure that issues are of high quality, include the necessary information to reproduce … etc. Such issues could receive another label, e.g. “confirmed” or “triaged”. Such issues would not be closed automatically by the bots. I think this is something where the community could help a lot, but the exact procedure needs to be defined and documented.
Finally: other successful projects, like the Godot Engine (with 5000+ issues) decided to split feature proposals into a separate repository, so issues on the main repository are reserved for bugs. This could be a good solution for ERPNext as well.
See:
and