Diff for "Bugs/Statuses"

Not logged in - Log In / Register

Differences between revisions 8 and 13 (spanning 5 versions)
Revision 8 as of 2008-07-13 22:14:40
Size: 2403
Editor: 92-237-59-186
Comment: page was renamed from Bugs/Statuses/Draft
Revision 13 as of 2009-05-28 16:34:41
Size: 2680
Editor: 92-237-59-186
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:

~-[[FrontPage|Launchpad Help]] > [[Bugs]] > Bugs statuses -~
Line 17: 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 24:
<<Anchor(bug-supervisor-only)>>  <<Anchor(bug-supervisor-only)>>
Line 34: Line 36:
= Next steps = = Next step =
Line 36: Line 38:
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]]. 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.

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 2024-05-09 16:28:14 by jugmac00)