Ubuntu Wiki

Bug statuses are a reflection of the current state of a bug report.

The status of a bug report can be modified by clicking on the current status in the yellow line, which will reveal a sub menu. You can then set a new status in the drop down box.

Below is a list of bug statuses, their meaning and when to use them:

• New:

  • Bugs are submitted with this status,

  • They sometimes lack information and

  • All of them should be untriaged

• Incomplete:

  • If you have to ask the reporter questions, set the bug to Incomplete

  • Ask the submitter to provide any necessary information in a comment, and make sure you subscribe yourself to the bug report so you will get any updates to the bug via e-mail.

  • Include(Bugs/Responses, , from="^== Incomplete bugs without a response from submitter ==", to="==")

• Invalid:

  • This status should be used when the bug report does not contain adequate information to determine whether or not it is a bug even if it is resolved for the reporter
  • It should be used conservatively as bugs marked as closed bugs no longer show up in default searches
  • Be sure to triple-check a bug before you invalidate it

• Confirmed:

  • Someone believes that that the report describes a genuine bug in enough detail that a developer could start working on a fix

  • Confirmed bugs require confirmation from someone other than the original reporter

  • This helps ensure that the bug is applicable to Ubuntu in general, and not a problem with the reporter's system, therefore...
  • Please don't confirm your own bugs!

• Triaged:

  • A member of [UbuntuBugControl] believes that the report describes a genuine bug in enough detail that a developer could start working on a fix

  • Use this when you are confident that it should be looked at by a developer and has enough information

• In Progress:

  • If you are working on fixing a bug, set it to In Progress so people know what's going on

  • In Progress bugs should be assigned to the person working on them

• Fix Committed:

  • For a bug against an upstream project: the fix is in CVS/SVN/bzr or committed to some place
  • For an Ubuntu package: the changes are pending and to be uploaded soon (it's what PENDINGUPLOAD was in Bugzilla)

  • Fix Committed is also used when an updated package exists in a -proposed repository i.e. feisty-proposed

  • Fix Committed is not to be used when a patch is attached to a bug

• Fix Released:

  • For bugs against upstream projects: a release tarball was announced and is publicly available
  • For package maintainers, a fix was uploaded to an official Ubuntu repository

    • This does not include -proposed i.e. feisty-proposed

    • Please don't hesitate to add a changelog as a comment, so people know what to look out for

• Won't Fix:

  • This status is sometimes used when the bug fix is too controversial
  • It is most often used for bugs with a release target that will not be fixed in that particular release but may be fixed later
  • It may also be used for feature requests that the developers do not want to implement

CategoryBugSquad