Diff for "Bugs/PrivateBugs"

Not logged in - Log In / Register
Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2009-01-30 12:30:42 →
Size: 1522
Editor: 92-237-59-186
Comment:
← Revision 2 as of 2009-01-30 12:31:20 → ⇥
Size: 1541
Editor: 92-237-59-186
Comment:
Deletions are marked like this. Additions are marked like this.
Line 28: Line 28:
||<tablestyle="width: 100%;">~-[[Projects/Announcements|< Project announcements]]-~||<style="text-align: right;">~-[[Bugs/Expiry|Bug expiry >]]-~|| ||<tablestyle="width: 100%;">~-[[Bugs/YourProject|< Using Launchpad to manage your project's bugs ]]-~||<style="text-align: right;">~-[[Bugs/Expiry|Bug expiry >]]-~||

Launchpad Help > Bugs > Private bugs

Contents

  1. Overview
    1. Private bugs
    2. Security-related bugs
  2. Next step

Overview

While most agree that "given enough eyeballs, all bugs are shallow", some bug reports should only be seen by a restricted group of people.

Launchpad gives you two levels of privacy for bug reports: private bugs and security-related bugs.

Private bugs

Anyone can mark an existing bug as private or, as a project owner, you can choose to have all bugs reported against your project marked private by default.

Once marked private, a bug report:

  • no longer appears in search results or bug listings, unless you have permission to view the full report
  • and the full report is visible only to the bug's direct subscribers, subscribers to the relevant project/series/package and the relevant owners/drivers.

Again, anyone can mark a bug report as a security vulnerability. Security-related bugs behave in a similar way to private bugs, except that Launchpad emails the project or distro's security contact with details of the bug report.

Next step

Let's first look at how Launchpad handles bugs that have gone stale.

< Using Launchpad to manage your project's bugs

Bug expiry >