Home » Support » Bug report » How to fill in the bug report
In order for us to quickly get an overview over the problems you are experiencing it is very imortant that you fill out the bug report carefully. Please read through the instructions below before submitting your bug report.
Write a clear and descriptive bug title
The bug title is important for us to get a rapid overview of the problem. Try to be as clear as possible but keep it reasonably short.
Submit detailed description of the problem
This is where you describe when and where the problem occured. Add as much information as possible including error messages, screenshots (can be added separately under File attachemnts/screen shots) and code samples.
Describe the steps to reproduce the problem
In order for us to understand the problem and confirm if it actually is a bug, we need to be able to re-create the problem in our test environment. Carefully describe what you were doing when the problem occured, what was your expected result and what actually took place, and in which order. (Before you submit the bug report you will be asked to state which version, browser etc you were using). Remember that our test team might never have seen the problem you describe, so try and be as explanatory as possible.
Select priority level
For us to make correct assessment of the severity of a confirmed bug, we need to know the impact of the problem for the customer. Please select a proper priority level according to the table below.
| Priority level |
Description |
Resolution type |
Critical
(Site crippled or
development stop) |
- Problem resulting in severely impaired business critical functionality or development stop, such as:
- Problem disabling users to reach site
- Severe security issue
- Business critical function not working
- Users are unable to complete purchase on site
- Significant performance degradation
- Development project cannot proceed
- Unrecoverable data loss of business critical data
|
Hotfix* or workaround
|
High
(Serious problem) |
- Problem resulting in slightly impaired business critical functionality or development difficulties, such as:
- Business critical function slightly impaired
- Non-business critical function not working
- Development project can proceed but at a higher cost using a workaround or alternative solution
|
Fix in the next version (minor or service release) and/or workaround |
Medium
(Medium priority) |
- Problem resulting in slightly impaired functionality or minor development difficulties
|
Possible fix in future
release |
Low
(Low priority) |
- An incident not requiring immediate consideration
|
Possible fix in future
release |
* = When are Hotfixes released
Hotfixes are issued on the current minor version and one minor version back. For example: if the current version is 4.5.1, Hotfixes are issued on all versions of 4.5 and 4.4. However, if the bug has been fixed in a later Service release on the same minor version, a Hotfix is not issued. For example, if a bug is found on 4.4.2 which is fixed in 4.4.3, a Hotfix will not be issued.
Comments made
No comments are made
You need to be logged in to make a comment