For small projects, sure. The probability that a bug will be reported is number of users * prominence of bug * the "reportability easiness" reported in you

For small projects, sure. The probability that a bug will be reported is number of users * prominence of bug * the "reportability easiness" reported in your article I have an open-source project with 100k active users, and I mostly handle issues myself, so I require the whole 9 yards of signing up for a GitHub account (reduces the number of lazy issues) and filling out ~10 questions in an issue template for both bug reports and feature requests. It works very well for increasing the average quality of bug reports and filtering duplicate, nonsensical, emotional, and information-lacking bug reports. If you're on the other side of the spectrum and are just begging for people to report bugs, then you should make it as simple as possible by allowing bug reports from all mediums (GitHub, email, forum, Twitter, phone call, whatever) and engage in the repetitive conversation it requires ("Can you send a screenshot?", "What does the error message say?", "Can you send your log.txt file?", etc.) But once the number of bug reports is more than you want to handle for the project's salary, you should implement methods to send users through a standard pipeline to avoid asking these questions every time.