LabVIEW Bug Reporting - Revision history

Gmoney: Updated the process for submitting a bug to NI to reflect the new SRM

2011-10-06T13:32:34Z

Updated the process for submitting a bug to NI to reflect the new SRM

← Older revision		Revision as of 13:32, 6 October 2011
Line 31:		Line 31:

	== Why Report Your Bug to National Instruments? ==		== Why Report Your Bug to National Instruments? ==
	The reason to report bugs to NI are simple – so they can be fixed! NI Applications Engineers are trained on filing good bug reports (called Corrective Action Requests, or CARs internally at NI) and have a well defined system in place to manage communication with customers. Applications Engineers also look for other opportunities to improve documentation, online literature, etc… as a result of your reported problem and other known LabVIEW issues. For these reasons it is important to report bugs to an AE when possible.		The reason to report bugs to NI are simple – so they can be fixed! NI Applications Engineers are trained on filing good bug reports (called Corrective Action Requests, or CARs internally at NI) and have a well defined system in place to manage communication with customers. Applications Engineers also look for other opportunities to improve documentation, online literature, etc… as a result of your reported problem and other known LabVIEW issues. For these reasons it is important to report bugs to an AE when possible.

	AEs can be reached by creating Service Requests. If you have an active service contract you can reach an AE directly by visiting www.ni.com/ask and choosing to call or email NI. All discussion forum posts that are made to the [http://forums.ni.com/ NI Discussion Forums] are monitored by Applications Engineers. Discussing your problem in any community (LAVA, NI Discussion Forums, etc…) is always encouraged and can often result in the community working together to find workaround and better define the problem. However, non-NI forums such as LAVA and info-LabVIEW are not officially monitored by NI employees, and are almost never monitored by an Applications Engineer. To ensure your problem is properly reported to NI R&D, please report your bug to an AE by creating a Service Request or posting a description of your problem to the NI Discussion Forums. Whether the problem is reported directly to NI, we recommend you post a new thread to the NI Discussion Forums on the issue (and include a CAR number if you have one) so that other users with the same problem have public record of it and any workarounds you may have found. To raise the visibility of the issue to other community members, you should also create an NI Discussion Forum thread and link it from the breakpoint monthly bug forum list (discussed below).		AEs can be reached by creating Service Requests. If you have an active service contract you can reach an AE directly by visiting www.ni.com/ask and choosing to call or email NI. All discussion forum posts that are made to the [http://forums.ni.com/ NI Discussion Forums] are monitored by Applications Engineers. Discussing your problem in any community (LAVA, NI Discussion Forums, etc…) is always encouraged and can often result in the community working together to find workaround and better define the problem. However, non-NI forums such as LAVA and info-LabVIEW are not officially monitored by NI employees, and are almost never monitored by an Applications Engineer. To ensure your problem is properly reported to NI R&D, please report your bug to an AE by creating a Service Request or posting a description of your problem to the NI Discussion Forums. Whether the problem is reported directly to NI, we recommend you post a new thread to the NI Discussion Forums on the issue (and include a CAR number if you have one) so that other users with the same problem have public record of it and any workarounds you may have found. To raise the visibility of the issue to other community members, you should also create an NI Discussion Forum thread and link it from the breakpoint monthly bug forum list (discussed below).
Line 37:		Line 37:
	==Reporting Bugs to National Instruments==		==Reporting Bugs to National Instruments==
	If you have a bug to report to NI, and the issue has not already been reported to NI, go to http://ni.com/ask to		If you have a bug to report to NI, and the issue has not already been reported to NI, go to http://ni.com/ask to
	submit a support request. ~~Select ''~~Reporting a Bug'' for your Question Type.		submit a support request. You can always call the Applications Engineers and open a new Service Request to report the bug. This option tends to be faster and more informative. If you call in then state your reason as "LabVIEW Bug Report" and then talk through your issue with the engineers.

			You can also select to Email the Applications Engineers as well. If you do choose to email your reported bug, then select "Reporting a Bug'' for your Question Type and fill in the other appropriate information. Make sure and be as descriptive as possible in the short field for the Question Summary as the next page will have a list of possible solutions based on those keywords. LabVIEW has been around for a while so make sure and check through this list of possible solutions as you are unlikely to be the first person to run across your issue. If the list of possible solutions doesn't work, then move on to the next step of the email process and try to be as descriptive as possible. As many details as you can put in as far as steps you have tried to solve the issue (i.e. trying it on a different computer, trying a different version of LabVIEW), attach any and all files that would be needed to reproduce your issue on a new computer at the bottom, and also detailed steps to reproduce. This makes the job of the Applications Engineers and NI R&D much easier when trying to diagnose the issue and will lead to hopefully a faster time to solution for you. After you enter in everything, continue with the process and send the email. NI Applications Engineer should follow up in a timely manner after you send it in.

	If you select Phone or E-mail NI, and you have a valid service contract, you will be routed to		If you select Phone or E-mail NI, and you have a valid service contract, you will be routed to

MichaelAivaliotis: /* External links */

2009-09-14T18:07:59Z

External links

← Older revision		Revision as of 18:07, 14 September 2009
Line 65:		Line 65:
	==External links==		==External links==
	*[http://forums.ni.com/ni/search?index=public&without=Re%3A&ratingend=&type=message&ratingstart=&q=Monthly+Bugs&page_size=10&phrase=&advanced=true&f=subject&f=body&one_or_more=&author=&board_id=BreakPoint&submitted=true&sort_by=-date Monthly bug thread on NI forums]		*[http://forums.ni.com/ni/search?index=public&without=Re%3A&ratingend=&type=message&ratingstart=&q=Monthly+Bugs&page_size=10&phrase=&advanced=true&f=subject&f=body&one_or_more=&author=&board_id=BreakPoint&submitted=true&sort_by=-date Monthly bug thread on NI forums]
	*[http://~~forums.~~lavag.org/~~Bug~~-~~Lists~~-~~f17.html~~ Bug Lists forum on LAVA]		*[http://lavag.org/forum/35-labview-bugs/ Bug Lists forum on LAVA]

	[[~~category~~:NI]]		[[Category:NI]]

MichaelAivaliotis: /* Posting a Bug Report on the LAVA Forums */

2009-09-14T18:06:58Z

Posting a Bug Report on the LAVA Forums

← Older revision		Revision as of 18:06, 14 September 2009
Line 50:		Line 50:
	There is a [http://lavag.org/forum/35-labview-bugs/ 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 [http://lavag.org/forum/7-labview-general/ LabVIEW General] discussion forum to discuss the issue with other LAVA members before creating a more official posting in the bug lists forum.		There is a [http://lavag.org/forum/35-labview-bugs/ 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 [http://lavag.org/forum/7-labview-general/ LabVIEW General] discussion forum to discuss the issue with other LAVA members before creating a more official posting in the bug lists forum.

	Bug report topics should be titled with a short description of the bug. The description of the topic should be used for status and [[CAR Number]]. For example, see the [http://~~forums.~~lavag.org/~~Move~~-on-disk-feature-crashes-~~LabVIEW-t9040.html~~ "Move on disk" feature crashes LabVIEW] bug. Notice how it has a clear title and description:		Bug report topics should be titled with a short description of the bug. The description of the topic should be used for status and [[CAR Number]]. For example, see the [http://lavag.org/topic/6103-move-on-disk-feature-crashes-labview/ "Move on disk" feature crashes LabVIEW] bug. Notice how it has a clear title and description:

	* Title: "Move on disk" feature crashes LabVIEW		* Title: "Move on disk" feature crashes LabVIEW

MichaelAivaliotis: /* Posting a Bug Report on the LAVA Forums */

2009-09-14T18:05:53Z

Posting a Bug Report on the LAVA Forums

← Older revision		Revision as of 18:05, 14 September 2009
Line 48:		Line 48:

	==Posting a Bug Report on the LAVA Forums==		==Posting a Bug Report on the LAVA Forums==
	There is a [http://~~forums.~~lavag.org/~~Bug~~-~~Lists~~-~~f17.html~~ 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 [http://~~forums.~~lavag.org/~~LabVIEW~~-~~General~~-~~f10.html~~ LabVIEW General] discussion forum to discuss the issue with other LAVA members before creating a more official posting in the bug lists forum.		There is a [http://lavag.org/forum/35-labview-bugs/ 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 [http://lavag.org/forum/7-labview-general/ LabVIEW General] discussion forum to discuss the issue with other LAVA members before creating a more official posting in the bug lists forum.

	Bug report topics should be titled with a short description of the bug. The description of the topic should be used for status and [[CAR Number]]. For example, see the [http://forums.lavag.org/Move-on-disk-feature-crashes-LabVIEW-t9040.html "Move on disk" feature crashes LabVIEW] bug. Notice how it has a clear title and description:		Bug report topics should be titled with a short description of the bug. The description of the topic should be used for status and [[CAR Number]]. For example, see the [http://forums.lavag.org/Move-on-disk-feature-crashes-LabVIEW-t9040.html "Move on disk" feature crashes LabVIEW] bug. Notice how it has a clear title and description:

MichaelAivaliotis: /* Reporting Bugs to National Instruments */

2009-09-14T18:04:23Z

Reporting Bugs to National Instruments

← Older revision		Revision as of 18:04, 14 September 2009
Line 45:		Line 45:
	are calling to report a bug.		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. When you get a CAR Number you should update your posting in the [http://~~forums.~~lavag.org/~~Bug~~-~~Lists~~-~~f17.html~~ Bug Lists] forum to include this CAR Number.		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. When you get a CAR Number you should update your posting in the [http://lavag.org/forum/35-labview-bugs/ Bug Lists] forum to include this CAR Number.

	==Posting a Bug Report on the LAVA Forums==		==Posting a Bug Report on the LAVA Forums==

Michael_Aivaliotis at 09:34, 8 October 2007

2007-10-08T09:34:31Z

← Older revision		Revision as of 09:34, 8 October 2007
Line 7:		Line 7:
	:*occurring in the development environment – for example, you click undo and LabVIEW crashes		:*occurring in the development environment – for example, you click undo and LabVIEW crashes
	:*occurring in during your program execution – for example, when you execute a property node with an unusual value, LabVIEW hangs		:*occurring in during your program execution – for example, when you execute a property node with an unusual value, LabVIEW hangs
			{{TOCright}}
	:'''Performance Problems:'''		:'''Performance Problems:'''
	:*operation is taking an unexpectedly long or short time to execute		:*operation is taking an unexpectedly long or short time to execute

Michael_Aivaliotis at 09:32, 8 October 2007

2007-10-08T09:32:10Z

← Older revision		Revision as of 09:32, 8 October 2007
Line 1:		Line 1:
	{{NIGuideline}}		{{NIGuideline}}
	<center>'''This article describes the process required for reporting bugs in LabVIEW.'''</center>		<center>'''This article describes the process required for reporting bugs in LabVIEW.'''</center>
	[[Image:bug.png\|~~thumb\|right~~]]		[[Image:bug.png\|frame]]
	LabVIEW Bugs are not limited to things which result in crashes of the software. Below are the most common categories of LabVIEW problems that should be reported to NI:		LabVIEW Bugs are not limited to things which result in crashes of the software. Below are the most common categories of LabVIEW problems that should be reported to NI:

Line 66:		Line 66:
	*[http://forums.ni.com/ni/search?index=public&without=Re%3A&ratingend=&type=message&ratingstart=&q=Monthly+Bugs&page_size=10&phrase=&advanced=true&f=subject&f=body&one_or_more=&author=&board_id=BreakPoint&submitted=true&sort_by=-date Monthly bug thread on NI forums]		*[http://forums.ni.com/ni/search?index=public&without=Re%3A&ratingend=&type=message&ratingstart=&q=Monthly+Bugs&page_size=10&phrase=&advanced=true&f=subject&f=body&one_or_more=&author=&board_id=BreakPoint&submitted=true&sort_by=-date Monthly bug thread on NI forums]
	*[http://forums.lavag.org/Bug-Lists-f17.html Bug Lists forum on LAVA]		*[http://forums.lavag.org/Bug-Lists-f17.html Bug Lists forum on LAVA]

			[[category:NI]]

MichaelAivaliotis: /* Posting a Bug Report on the LAVA Forums */

2007-09-26T05:43:09Z

Posting a Bug Report on the LAVA Forums

← Older revision		Revision as of 05:43, 26 September 2007
Line 48:		Line 48:

	==Posting a Bug Report on the LAVA Forums==		==Posting a Bug Report on the LAVA Forums==
	There is a [http://forums.lavag.org/Bug-Lists-f17.html Bug Lists] forum on LAVA. This should be used for reporting confirmed bugs with a [[CAR Number]]. If a posting in the ~~[http://forums.lavag.org/Bug-Lists-f17.html Bug_Lists]~~ forum is determined to not be a bug, it will be moved into another forum. Also, you can use the [http://forums.lavag.org/LabVIEW-General-f10.html LabVIEW General] discussion forum to discuss the issue with other LAVA members before creating a more official posting in the ~~[http://forums.lavag.org/Bug-Lists-f17.html Bug Lists]~~ forum.		There is a [http://forums.lavag.org/Bug-Lists-f17.html 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 [http://forums.lavag.org/LabVIEW-General-f10.html LabVIEW General] discussion forum to discuss the issue with other LAVA members before creating a more official posting in the bug lists forum.

	Bug report topics should be titled with a short description of the bug. The description of the topic should be used for status and [[CAR Number]]. For example, see the [http://forums.lavag.org/Move-on-disk-feature-crashes-LabVIEW-t9040.html "Move on disk" feature crashes LabVIEW] bug. Notice how it has a clear title and description:		Bug report topics should be titled with a short description of the bug. The description of the topic should be used for status and [[CAR Number]]. For example, see the [http://forums.lavag.org/Move-on-disk-feature-crashes-LabVIEW-t9040.html "Move on disk" feature crashes LabVIEW] bug. Notice how it has a clear title and description:

MichaelAivaliotis at 05:09, 25 September 2007

2007-09-25T05:09:39Z

← Older revision		Revision as of 05:09, 25 September 2007
Line 1:		Line 1:
	{{~~guideline~~}}		{{NIGuideline}}
	<center>'''This article describes the process required for reporting bugs in LabVIEW.'''</center>		<center>'''This article describes the process required for reporting bugs in LabVIEW.'''</center>
	[[Image:bug.png\|thumb\|right]]		[[Image:bug.png\|thumb\|right]]

MichaelAivaliotis at 05:03, 25 September 2007

2007-09-25T05:03:10Z

← Older revision		Revision as of 05:03, 25 September 2007
Line 1:		Line 1:
			{{guideline}}
	<center>'''This article describes the process required for reporting bugs in LabVIEW.'''</center>		<center>'''This article describes the process required for reporting bugs in LabVIEW.'''</center>
	[[Image:bug.png\|thumb\|right]]		[[Image:bug.png\|thumb\|right]]