- Please report any bugs via the appropriate Discord channel 🐞 bug-reporting
- This channel will only accept new messages that include a http link (either to fixture, team, or rider.) Others are automatically deleted. This is done to help speed up support time by the race committee - “help us to help you!”
- When reporting a bug, the more information we have the quicker we can assist in helping, please try to report with information such as the following :-
- Title: Keep it brief and use correct terms. A best practice is to include the name of the feature where you found an issue. A good example could be 'CHALLENGE - Unable to challenge [XXX] team'.
- Description/summary: If you feel the name is not sufficient, explain the bug in a few words.
- Environment: Depending on your device, browser, operating system. Your user account, team you manage, are you vice or captain?
- Source URL: Make it easy for everyone to spot the problem by including the URL of the page where you found the bug. Links to riders, fixtures, results, etc.
- Visual proof: A picture is worth a thousand words. Although it might not be enough, a visual element like a screenshot or a video will help your developers understand the problem better and faster.
- Steps to reproduce: A screenshot is a proof that you had a problem, but keep in mind that your developer might not be able to reproduce the bug. Make sure to describe, with as much detail as possible, the steps you took before you encountered the bug.
- Expected result vs. actual result: Explain what results you expected - be as specific as possible. Just saying "the app doesn’t work as expected" is not useful. It's also helpful to describe what you actually experienced.