A good bug report should contain only one bug and be clear and concise yet informationally dense. It should contain environment details and user steps that allow the developer to reproduce the bug on his side.
Take a screenshot or screen recording of the issue you are facing.
Click on the blue button found in the bottom right-hand corner:
Fill out the required information and upload the screen recording/screenshot
And lastly, submit your bug report.
Do's and Don'ts when Reporting a Bug
Bug Reporting Do’s
DO read your report when you’re done. Make sure it is clear, concise and easy to follow.
DO be as specific as possible and don’t leave room for ambiguity.
DO reproduce the bug a few times and try to eliminate any unnecessary steps.
If you have found a workaround or additional steps that make the bug behave differently, DO include that in your report.
Bug Reporting Don’ts
DON’T include more than one bug in your report. Tracking the progress and dependencies of individual bugs becomes an issue when there are several bugs in the report.
DON’T be critical or blaming. Bugs are inevitable and not always easy to fix.
DON’T speculate on what’s causing the bug. This can send the developer on a wild goose chase, so stick to the facts.
DON’T post anything that is not a bug. Developers love to hear your feedback, but posting it in the wrong channel will only clutter their workflow and cause unnecessary delays.