@revant_one I partially agree, but the problem I see, is ERPNext is huge!
We have unitary tests, and they doesn’t cover 100% of the system, neighter edge cases like properly integrations between modules.
Also we have the demo.erpnext.org, where we can keep an eye, to understand what’s going on.
But, it still doesn’t solve the problem!
My suggestion with sentry.io, is because we can collect usefull information from everywhere, and keep this information open (if there’s not sensible data).
Also, sentry, has a nice way to organize reincident bugs, what can define some level of priorization.
But, even this has they own problems (it’s my technical side, making a technical proposition, that if not properly implemented, will exclude users voice from the equation)