Skip to main content
Jump to: navigation, search

Eclipse/Bug Tracking

< Eclipse
Revision as of 09:24, 7 January 2010 by Daniel (Talk | contribs) (Target Milestones)


The Eclipse Project uses Eclipse Bugzilla for bug tracking. This page provides details on how the Eclipse project uses bugzilla.

Bugzilla Fields


The Eclipse Project uses the following values for the bugzilla Product field:

  • Platform
  • JDT
  • PDE
  • E4
  • Incubator

Target Milestones

The 'Target Milestone' field lists the Milestone or Release in which a bug is intended to get fixed or was first fixed. The fix can be assumed to be present in all milestones or releases after that point, unless otherwise specified in the bug. The notation used is as follows:

  • x.y.z - indicates a final release build in which the fix/enhancement was made
  • x.y.z M# - indicates a milestone build in which the fix/enhancement was made
  • x.y.z RC# - indicates a release candidate build in which the fix/enhancement was made
  • 2.0 F# - indicates a release candidate build from the 2.0 release. The term freeze was replaced with release candidate in subsequent releases
  • x.y.z+ - indicates the fix was made after the x.y.z release, and was released into the Rx_y_maintenance branch in CVS corresponding to that release. If a hypothetical x.y.(z+1) release were to occur, it would contain the release, but no such release is scheduled. For example 3.4.2+ indicates the fix was released in the R3_4_maintenance branch in CVS sometime after the 3.4.2 release, and would be included in a theoretical 3.4.3 release if such a release occurred.


Priority is set by the committer or contributor that the bug is assigned to, or by the component owner. This roughly indicates the importance of the bug/enhancement relative to the other bugs/enhancements owned by the committer or component.

Priority Definition
Must fix for next release. Literally. We will slip dates for P1's, so use sparingly.
Very important for next release or milestone. Nearly all P2's should be released, so do not over use.
Of normal importance. Default starting point. While triaging a bug it is good to consider its priority and adjust higher or lower if appropriate.
Less important. Would like to fix the bug, time permitting.
A valid bug, but no plans to investigate further or fix. All 'P5' bugs also imply "helpwanted", but "helpwanted" can also be used on any other priority.


Severity is set by the person who reported the bug. The bug owner can change the severity or request the originator do so if their description of the problem is inconsistent with the definition of the severity. However, the severity represents the originator's perspective and should not be changed by others purely because they have a different perspective. For example if the originator only uses Eclipse for spell-checking, and the spell-checking function is not working, they can fairly say the bug is blocking even though from the committer's perspective it is only a major problem.

Severity Definition
Blocks development and/or testing work. No workaround exists.
Crashes, loss of data, severe memory leak.
Major loss of function.
Regular issue, some loss of functionality under specific circumstances.
Minor loss of function, or other problem where easy workaround is present.
Cosmetic problem such as misspelled words or misaligned text.
Request for enhancement.

Back to the top