Seems like the issue is... issues. Some projects get so popular that it&#x27;s a full time job just to respond to issues that lack information.<p>I&#x27;ve been in software for a long time. There&#x27;s no tool that solves this problem. People who don&#x27;t know your software don&#x27;t know how to report issues. They don&#x27;t know the keywords or nomenclature to search for pre-existing error messages either.<p>Switching to another tool won&#x27;t solve this problem they&#x27;re having. Typical engineers - they think issue templates will help. No. I&#x27;ll just fill in whatever gets me past the validation cos I&#x27;m frustrated.<p>This might be unpopular, but you&#x27;re under no obligation to answer those issues or even have a public issue tracker at all. Turn the issue tracker off if it&#x27;s frustrating, and use a private issue tracker for the core team. Or find some students that want to break into open source and have them be 1st level triage for your issues. It&#x27;s a people problem, not a technology problem.<p>Too many developers forget that software development, even open-source, is 20% code and 80% people. Documentation and support are a huge part of software. And software only goes so far to solving that in my experience.