The Meaning of Issue Fields

  • Version - version of the IDE in which you encountered the problem. For the latest nightly builds, use Dev. In case you don't know, just select current.
  • Product and Component - together these usually specify a NetBeans module in which the error occurred, but the details are complicated. Most people should just select IDE for the product and Code for the component and someone will move the issue to the right component later.
  • __Platform_ - select the platform you were using when the problem occurred. If you are able to reproduce it on multiple platforms, or you are sure the behavior is platform independent, use All.
  • OS - similar to the Platform.
  • Priority - use this field to indicate the urgency and severity of the issue. Look at Bug Priority Guidelines to set the priority level appropriately. If you're still in doubt, just select P3.
  • Issue Type - if you are reporting a problem select DEFECT. If you are requesting a feature or enhancement select ENHANCEMENT.
  • Assigned To - unless you're absolutely sure who this issue should be assigned to, leave this field blank. The bug will be automatically assigned to the component (subcomponent) owner.
  • Cc - enter an optional space-separated list of login names you want to be notified about any subsequent changes of issue. You as the reporter will be notified automatically, so there's no need to add yourself. Arbitrary email addresses are not accepted by the system.
  • URL - if there is a URL relevant to this issue, you can type it here.
  • Summary - a brief (one sentence) description of the issue (follow The Rules)
  • Description - a detailed description of the problem. The description should if possible include all information needed to reproduce the problem (follow The Rules). Add large files as attachments after submitting.
Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo