All bug reports should contain enough detail to be replicated. This makes the replication process much more efficient, which in turn helps the customer support team and development team to resolve the issue more quickly.
All bug reports must include the following.
- A description of the issue
- The actions you took
- What you expected to happen
- What actually happened
- Other information or notes which may be pertinent
If relevant, you should include screenshots, screencasts, URLs, advert IDs and/or retailer names.
Example of a bug report lacking sufficient detail
Retailers can't update their brands
Example of a great bug report
One of our retailers, Bob's Bikes, cannot update the brands of their product adverts.
To replicate:
- Login to Bob's Bikes account on BEAU
- Search for any advert e.g. Ad ID: 100000001
- Edit the advert, go to the first page
- Try to update the brand
Expected result:
User should be able to enter/update the brand.
Actual result:
The brand field is not displaying on the advert (see attached screenshot)
Other information:
- I've checked the taxonomy 'Road Bikes' and brand is enabled.
- This issue only appears to be affecting Bob's Bikes; I've checked other accounts and I can update the brands of their adverts.
In need of some extra guidance? You can submit your bug reports directly through our Support portal. The form has been broken down into sections to assist you with reporting a bug.
Related articles