LabVIEW Bug Reporting
This article describes the process required for reporting bugs in LabVIEW.
Requirements of a Good Bug Report
Good bug reports should always include the following:
- Steps to reproduce
- What happened
- What you expected to happened
This information is needed to confirm that what you are seeing is actually a bug and to help figure out what is causing the buggy behavior. It is also a great idea to include any example code that demonstrates the bug and/or screenshots of the bug.
Reporting Bugs to National Instruments
If you have a bug to report to NI, go to http://ni.com/ask to submit a phone support request. If you specify that you are reporting a bug, you should be connected to an Applications Engineer who can help you by filing the appropriate bug report.
If you select Phone NI, and you have a valid service contract, you will be routed to Applications Engineers who can file the appropriate bug report. If you do not have a valid service contract, you are routed to an intermediary person who can pass you through to an Applications Engineer, provided you are calling to report a bug.
If your bug is in fact a bug, ask for a CAR Number -- this is how your bug is uniquely identified and can be used to track its status.
Posting a Bug Report on the LAVA Forums
There is a Bug Lists forum on LAVA. This should be used for reporting confirmed bugs with a CAR Number. If a posting in the Bug Lists forum is determined to not be a bug, it will be moved into another forum. Also, you can use the LabVIEW General discussion forum to discuss the issue with other LAVA members before creating a more official posting in the Bug Lists forum.