A bug report will include the following parts:
- Clear title: Highlight what’s wrong and related functions or features.
- Steps to reproduce the issue: Make it as detail as possible and attach images or videos if necessary. A picture is worth a thousand words.
- Actual result
- Expected result: It’s better if we could link to documentation or official technical information.
- Other Notes (if necessary)
- Operating System
- Device
- Browser
- Version
- Severity of the bug
| Critical | The bug prevents critical functionality within the app from working. This includes crashing, freezing for which no workaround is possible and a fix is required immediately. |
| High | The bug affects major functionality within the app from working. However, high-priority bugs can be avoided with a workaround. |
| Medium | The bug does not cause a failure and does not interfere with the fluent work of the system and programs. It has an easy workaround. |
| Low | The bug does not affect functionality or data, or require a workaround. It is a result of non-conformance to a standard that does not impact productivity – typing errors/ aesthetic inconsistencies. |
| Usability | A suggestion that would improve how an app is understood, learnt and used efficiently. |
One bug per report