Bug Report Guidelines Read Before You Post
Summary
The BrickBit Community announcement outlines mandatory bug report guidelines and a reusable template. It explains requirements for neat posts, ensuring reports are unique, including steps to reproduce, using correct tags, and creating only one post per bug. Template fields include Issue, Steps to Reproduce, and Affected Areas.
Guidelines
Posts must be written neatly (use template below if necessary),
Before posting, ensure you have given a reasonable effort to ensure that your report is unique (as in not reporting something present in a previous post by another user),
Include instructions to reproduce the reported bug where possible,
Use correct tags,
Only create one post per bug report - this makes our job significantly easier,
Template (fill in your own details)
Issue
Description of your issue goes here.
Steps to Reproduce
Steps to reproduce your issue goes here.
Remove this segment if your bug is apparent without action.
Affected Areas
If your issue is on the site, list all affected pages here.
Otherwise, if your issue is in any officially distributed software, list which specific BrickBit application your issue is present in.
Guidelines
- Posts must be written neatly (use template below if necessary)
- Before posting, ensure you have given a reasonable effort to ensure that your report is unique (as in not reporting something present in a previous post by another user)
- Include instructions to reproduce the reported bug where possible
- Use correct tags
- Only create one post per bug report - this makes our job significantly easier
Template (fill in your own details) ```
Issue
Description of your issue goes here.
Steps to Reproduce
Steps to reproduce your issue goes here.
Remove this segment if your bug is apparent without action.
Affected Areas
If your issue is on the site, list all affected pages here.
Otherwise, if your issue is in any officially distributed software, list which specific BrickBit application your issue is present in.```
