Diff for "Bugs/Statuses"

Not logged in - Log In / Register

Differences between revisions 4 and 14 (spanning 10 versions)
Revision 4 as of 2008-05-20 17:27:17
Size: 2064
Editor: 77-100-239-119
Comment:
Revision 14 as of 2010-09-20 08:27:58
Size: 2892
Editor: nat74
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">[[TableOfContents]]|| ## page was renamed from Bugs/Statuses/Draft
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||
Line 3: Line 4:
[[Anchor(bug-statuses-in-launchpad)]] ~-[[FrontPage|Launchpad Help]] > [[Bugs]] > Bugs statuses -~

<<
Anchor(bug-statuses-in-launchpad)>>
Line 5: Line 8:

Anyone can set the status of a bug in Launchpad, making it easy for them to become involved in your project's bug triage.
Line 10: Line 11:
Optionally, if your project has a high number of bug reports, you may want to add an extra layer of quality control to your bug triage. Two additional bug statuses - ''Triaged'' and ''Won't Fix'' - are available only to your project's [:Bugs/BugContactRole:bug contact], owners and drivers. Optionally, if your project has a high number of bug reports, you may want to add an extra layer of quality control to your bug triage. Whereas anyone can set most of the bug statuses, which makes it easy for new contributors to get involved, there are two additional bug statuses - ''Triaged'' and ''Won't Fix'' - that are available only to your project's owner, bug supervisor and the relevant drivers.
Line 12: Line 13:
[[Anchor(available-to-everyone)]] <<Anchor(available-to-everyone)>>
Line 16: Line 17:
 * '''Incomplete:''' the bug report is incomplete and needs more information before it can be triaged.  * '''Incomplete:''' the bug report is incomplete and needs more information before it can be triaged. Bugs in this state are considered for [[Bugs/Expiry|expiry]].
Line 18: Line 19:
 * '''Confirmed:''' a member of the community believes that this report describes a genuine bug in enough detail that a developer could start work on a fix.  * '''Confirmed:''' a member of the community other than the original reporter believes that this report describes a genuine bug in enough detail that a developer could start work on a fix.
Line 22: Line 23:
 * ''Under consideration for removal:'' '''Opinion:''' there is a difference of opinion about the bug and everyone is free to continue the discussion, however, the project maintainers consider the issue closed.
Line 23: Line 25:
[[Anchor(bug-supervisor-only)]] <<Anchor(bug-supervisor-only)>>
Line 29: Line 31:
[[Anchor(translating-external-bug-statuses)]] = Translating external bug statuses =
Line 31: Line 33:
= Next steps = When Launchpad watches a bug report in an external tracker - such as Bugzilla or Sourceforge - it translates that bug's status information into the equivalent Launchpad status.
Line 33: Line 35:
Launchpad helps you to stay on top of the bugs you're interested in, both by email and Atom feeds. Let's take a look at [:Bugs/Subscriptions:bug subscriptions]. See our [[Bugs/Statuses/External|page on external bug statuses]].

= Next step =

If you're working on a fix to a bug and hosting that code in Launchpad, you can [[Bugs/BugBranchLinks|link from the bug report directly to the branch of code]].

||<tablestyle="width: 100%;"> ~-[[Bugs/MultiProjectBugs|< Multi-project bugs]] -~ ||<style="text-align: right;"> ~- [[Bugs/BugBranchLinks|Linking bug reports to branches >]] -~ ||

Launchpad Help > Bugs > Bugs statuses

Bug statuses in Launchpad

Launchpad's bug tracker offers you seven main bug statuses that reflect each stage of a bug's lifecycle, from initial report to resolution.

Optionally, if your project has a high number of bug reports, you may want to add an extra layer of quality control to your bug triage. Whereas anyone can set most of the bug statuses, which makes it easy for new contributors to get involved, there are two additional bug statuses - Triaged and Won't Fix - that are available only to your project's owner, bug supervisor and the relevant drivers.

Available to everyone

  • New

  • Incomplete: the bug report is incomplete and needs more information before it can be triaged. Bugs in this state are considered for expiry.

  • Invalid: the report describes the software's normal behaviour, or is unsuitable for any other reason.

  • Confirmed: a member of the community other than the original reporter believes that this report describes a genuine bug in enough detail that a developer could start work on a fix.

  • In Progress: a developer has taken responsibility to fix the bug and has begun work.

  • Fix Committed: a developer has committed his/her fix to the project's codebase.

  • Fix Released: a new version of the software, featuring the bug fix, has been released.

  • Under consideration for removal: Opinion: there is a difference of opinion about the bug and everyone is free to continue the discussion, however, the project maintainers consider the issue closed.

Only available to the bug supervisor

  • Triaged: the bug supervisor considers that the bug report contains all information a developer needs to start work on a fix.

  • Won't Fix: this is acknowledged as a genuine bug but the project has no plans to fix it.

Translating external bug statuses

When Launchpad watches a bug report in an external tracker - such as Bugzilla or Sourceforge - it translates that bug's status information into the equivalent Launchpad status.

See our page on external bug statuses.

Next step

If you're working on a fix to a bug and hosting that code in Launchpad, you can link from the bug report directly to the branch of code.

< Multi-project bugs

Linking bug reports to branches >

Bugs/Statuses (last edited 2010-09-20 08:27:58 by nat74)