About Bug Reporting
A software bug is essentially any aspect of the system that is not functioning as it was designed. Bugs are often categorized by their severity and impact.
Class I bugs:
Class I bugs are rare, but if one does come up, we go into an "all hands on deck mode" and do no other work until the bug is fixed.
- Server Crash / Users cannot log in
- Inaccurate financial data (note, this is not to be confused with auditing!)
- Data integrity issues
- Errors that cause a transaction to stop, and there is no work around
Class II bugs:
Class II bugs don't keep you from running the business, but it would be better if they were taken care of.
- Error messages that do not impact processing (e.g. the function is working while still causing an error)
- Reviewing a non-critical issue with an existing report.
- Transaction issues, but there is a work around.
- Cosmetic issues (e.g. something in the UI or a printed report is formatted incorrectly)
In the Tech Support vs. Consulting lesson, when we talk about "changing the priority of a Class II bug." This means taking something in the Class II category and getting it fixed right now. If you wait, it will be fixed for free at some point. If you want it fixed now, we can do it, but that's not free.