Trackers - Reporting Bugs
For the 2019 Beta, the Trackers tab will be used only for filing bugs (different than the past few seasons). For reporting progress, see Reporting Progress.
While we will certainly accept and respond to bugs in either location, for 2019 we would prefer bugs for WPILib C++/Java components (libraries, VSCode, Shuffleboard, etc.) be submitted to the appropriate GitHub repositories.
The bug tracker is used for reporting bugs you discover in WPILib or other FRC software. If you are not sure if particular behavior is a bug or not, err on the side of reporting the bug (or at least posting in the Discussion section).
On the Trackers tab, click on Bugs to reach the Bug Tracker. To Submit a new bug, click Submit New Artifact. The fields of the artifact are:
- Title - Give your bug a meaningful title which describes the issue
- Description - Describe the bug including observed behavior, expected behavior and steps to reproduce
- Reported By - Enter your TeamForge user name or click the silhouette to open the selector where you can select your username.
- Category - Select the appropriate affected software from the dropdown list (LabVIEW WPILib, Java WPILib, Driver Station, etc.)
- Reported in Release - Select which version of the file you were using, if available.
- Priority - If desired you may estimate a priority based on bug severity. Leaving at the default priority does not mean the bug will not be addressed. All new bugs are analyzed by the Control System team and assigned an appropriate priority.
- Status - When reporting a new bug this should be left as Open.
- Assigned To - When reporting a bug this should be left blank. The Control System team uses this field to indicate who is working on a given artifact.
- Attachment - Attach any additional file that may be appropriate, examples of appropriate files would be a patch for the bug, code to reproduce the bug (single file or zip) or an image of the bug (if appropriate/necessary).