launchpad help|
Size: 1541
Comment:
|
Size: 2039
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 15: | Line 15: |
| Once marked private, a bug report: | Once someome marks a bug report as private: |
| Line 17: | Line 17: |
| * 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. |
* it no longer appears in search results or bug listings, unless you have permission to view the full report * indirect subscribers to the bug -- i.e. people who are subscribed to all bugs related to the project, package or distro -- become direct subscribers * the full report is visible only to the bug's direct subscribers and the relevant owners/drivers. This means that, after the bug has been marked private, no new people can view or subscribe to it without an invitation from an existing direct subscriber but that anyone subscribed -- directly or indirectly -- before the bug was private will continue to have access. |
| Line 22: | Line 25: |
| 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. | 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 * indirect subscribers are not converted to direct subscribers, giving you greater control over who can view the report. |
| Line 26: | Line 32: |
| Let's first look at how Launchpad handles [[Bugs/Expiry|bugs that have gone stale]]. | Let's look at how Launchpad handles [[Bugs/Expiry|bugs that have gone stale]]. |
| Line 28: | Line 34: |
| ||<tablestyle="width: 100%;">~-[[Bugs/YourProject|< Using Launchpad to manage your project's bugs ]]-~||<style="text-align: right;">~-[[Bugs/Expiry|Bug expiry >]]-~|| | ||<tablestyle="width: 100%;">~-[[Bugs/YourProject|< Tracking your project's bugs in Launchpad]]-~||<style="text-align: right;">~-[[Bugs/Expiry|Bug expiry >]]-~|| |
Launchpad Help > Bugs > Private bugs
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 someome marks a bug report as private:
- it no longer appears in search results or bug listings, unless you have permission to view the full report
- indirect subscribers to the bug -- i.e. people who are subscribed to all bugs related to the project, package or distro -- become direct subscribers
- the full report is visible only to the bug's direct subscribers and the relevant owners/drivers.
This means that, after the bug has been marked private, no new people can view or subscribe to it without an invitation from an existing direct subscriber but that anyone subscribed -- directly or indirectly -- before the bug was private will continue to have access.
Security-related bugs
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
- indirect subscribers are not converted to direct subscribers, giving you greater control over who can view the report.
Next step
Let's look at how Launchpad handles bugs that have gone stale.
