launchpad help|
Size: 5782
Comment:
|
← Revision 24 as of 2012-09-06 17:50:21 ⇥
Size: 4651
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| '''DRAFT: this page is a work in progress. Please [:Feedback:seek further help] or check the [:TitleIndex:wiki index] for a complete page on this topic.''' | ~-[[FrontPage|Launchpad Help]] > [[Bugs]] > Your project -~ |
| Line 3: | Line 3: |
| ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''[[BR]][[TableOfContents]]|| | ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| |
| Line 13: | Line 13: |
| [https://bugs.launchpad.net/zope3/+bug/98275 Bug 98275] is a great example. It is one bug report, with one bug number, but it has a different status, importance and assignee in each context. | [[https://bugs.launchpad.net/zope3/+bug/98275|Bug 98275]] is a great example. It is one bug report, with one bug number, but it has a different status, importance and assignee in each context. |
| Line 15: | Line 15: |
| ||<tablestyle="font-size: 0.8em; width:30%; background:#F1F1ED; margin: 1em 1em 1em 0;" style="padding:0.5em;">attachment:zeo-multi-context-bug.png|| | ||<tablestyle="font-size: 0.8em; width:30%; background:#F1F1ED; margin: 1em 1em 1em 0;" style="padding:0.5em;">{{attachment:zeo-multi-context-bug.png}}|| |
| Line 18: | Line 18: |
| This table appears at the top of the bug report, showing that it affects three projects and different series (lines of development towards a release) within those projects. In this case, each of the affected projects uses Launchpad's bug tracker. However, Launchpad can just as happily monitor the progress of the same bug in external trackers, as shown in [https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/122590 bug 122590]. | This table appears at the top of the bug report, showing that it affects three projects and different series (lines of development towards a release) within those projects. In this case, each of the affected projects uses Launchpad's bug tracker. However, Launchpad can just as happily monitor the progress of the same bug in external trackers, as shown in [[https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/122590|bug 122590]]. |
| Line 20: | Line 20: |
| ||<tablestyle="font-size: 0.8em; width:30%; background:#F1F1ED; margin: 1em 1em 1em 0;" style="padding:0.5em;">attachment:gnome-external-watch.png|| | ||<tablestyle="font-size: 0.8em; width:30%; background:#F1F1ED; margin: 1em 1em 1em 0;" style="padding:0.5em;">{{attachment:gnome-external-watch.png}}|| |
| Line 27: | Line 27: |
| When you [:Projects/Registering:registered your project] in Launchpad, you had the option to specify where its bugs are tracked. If you chose an option other than ```Bugs are tracked in Launchpad```, you now need to activate the Launchpad bug tracker for your project. | When you [[Projects/Registering|registered your project]] in Launchpad, you had the option to specify where its bugs are tracked. If you chose an option other than ```Bugs are tracked in Launchpad```, you now need to activate the Launchpad bug tracker for your project. |
| Line 29: | Line 29: |
| Follow the ```Change details``` link in the ```Actions``` menu on your project's overview page. | Follow the ```Change details``` link on your project's overview page. |
| Line 31: | Line 31: |
| ||<tablestyle="font-size: 0.8em; width:30%; background:#F1F1ED; margin: 1em 1em 1em 0;" style="padding:0.5em;">attachment:bugs-are-tracked.png|| | ||<tablestyle="font-size: 0.8em; width:30%; background:#F1F1ED; margin: 1em 1em 1em 0;" style="padding:0.5em;">{{attachment:bugs-are-tracked.png}}|| |
| Line 34: | Line 34: |
| You can also choose whether Launchpad should automatically expire inactive bugs. There's more on what Launchpad considers an inactivate bug in our article on [:BugExpiry:bug expiry]. | You can also choose whether Launchpad should automatically expire inactive bugs. There's more on what Launchpad considers an inactive bug in our article on [[BugExpiry|bug expiry]]. |
| Line 40: | Line 40: |
| [:Feedback:Get in touch] to see if we can help. | [[Feedback|Get in touch]] to see if we can help. |
| Line 42: | Line 42: |
| == Bug and security contacts == | == Bug supervisors == |
| Line 44: | Line 44: |
| ||<tablestyle="float: right; font-size: 0.8em; width:30%; background:#F1F1ED; margin: 1em 0 1em 1em;" style="padding:0.5em;">attachment:bug-and-security-contact-actions.png|| ||<style="text-align: center;">'''Setting your project's bug and security contacts'''|| |
|
| Line 47: | Line 45: |
| The next step is to choose which individuals or teams you want to occupy the two bug management roles: | * '''bug supervisor:''' handles day to day management and triage Many projects [[Teams/Registering|create specific teams]] to act as the bug supervisor, allowing several people to triage bugs without gain. |
| Line 49: | Line 49: |
| * '''[:Bugs/BugContactRole:bug contact]:''' handles day to day management and triage * '''[:Bugs/SecurityContactRole:security contact]:''' receives security-related bug notifications. Many projects [:Teams/Registering:create specific teams] to act as bug and security contacts, allowing several people to share the work. |
|
| Line 54: | Line 50: |
| To set your project's bug and security contacts, visit its bug overview page - for example: https://bugs.launchpad.net/inkscape - and follow the links in the ```Actions``` menu. | |
| Line 58: | Line 53: |
| === The bug contact role === | |
| Line 60: | Line 54: |
| Your project's bug contact can do a few things that other people can't: | === The bug supervisor's role === You may want to give some people extra bug editing privileges: The bug supervisor's role is to manage the planning of bug work and the triage of newly reported bugs. Launchpad helps them do this by giving them access to: |
| Line 63: | Line 61: |
| * set the privacy of a bug * mark bug reports as security issues * view private bugs * set certain [Bugs/Statuses:bug statuses]. A bug contact is also, by default, an email [:Bugs/Subscriptions:subscriber] to the project's bugs. A bug contact can unsubscribe from email notifications. |
* set the importance of a bug * set certain [[Bugs/Statuses|bug statuses]]. |
| Line 70: | Line 64: |
| === The security contact role === Your project's security can view reports marked as security issues. They also receive email notifications when a bug report is marked as a security issue. = Bugs overview page = Your project's bugs overview page gives you a snapshot of the current status of all the bugs associated with your project. Here's the bugs overview page for the [https://launchpad.net/inkscape Inkscape] vector drawing tool. ||<tablestyle="font-size: 0.8em; width:30%; background:#F1F1ED; margin: 1em 1em 1em 0;" style="padding:0.5em;">attachment:inkscape-bugs-overview.png|| ||<style="text-align: center;">'''Inkscape's bugs overview page'''|| |
To set your project's bug supervisor, visit its bug overview page - for example: https://bugs.launchpad.net/inkscape - then choose the edit link next the the bug supervisor role listed on the page. |
| Line 85: | Line 68: |
| You can stay on top of your project's bugs activity by email or Atom feed. Let's take a look at [:Bugs/Subscriptions:bug subscriptions]. | Now you've set up the basics, you're ready to start managing your project's bug reports in Launchpad. However, let's first look at how Launchpad [[Bugs/BugHeat|tracks the hottest bugs]]. ||<tablestyle="width: 100%;">~-[[Projects/Announcements|< Project announcements]]-~||<style="text-align: right;">~-[[Bugs/BugHeat|Bug heat >]]-~|| |
Launchpad Help > Bugs > Your project
Overview
Launchpad's bug tracker is unique: it can track how one bug affects different communities.
When you share free software, you share its bugs. This means that free software bugs may be reported in one project but originate in another entirely, whilst affecting several more.
Launchpad handles this by making every bug available to every project and distribution that uses the bug tracker. Rather than treating each project as an island, with an isolated list of bug reports, Launchpad allows interested groups to work together in search of a fix.
Bug 98275 is a great example. It is one bug report, with one bug number, but it has a different status, importance and assignee in each context.
|
This bug affects different projects and series |
This table appears at the top of the bug report, showing that it affects three projects and different series (lines of development towards a release) within those projects. In this case, each of the affected projects uses Launchpad's bug tracker. However, Launchpad can just as happily monitor the progress of the same bug in external trackers, as shown in bug 122590.
|
Watching a bug tracked elsewhere |
Here, the bug report in Launchpad is about Ubuntu's package of the Gnome Panel. However, there's also a link to the bug as tracked in Gnome's Bugzilla, along with its status there. This lets the Ubuntu desktop bugs team monitor the progress upstream and implement their fix when it becomes available.
Getting started
When you registered your project in Launchpad, you had the option to specify where its bugs are tracked. If you chose an option other than Bugs are tracked in Launchpad, you now need to activate the Launchpad bug tracker for your project.
Follow the Change details link on your project's overview page.
|
Choosing Launchpad as your bug tracker |
You can also choose whether Launchpad should automatically expire inactive bugs. There's more on what Launchpad considers an inactive bug in our article on bug expiry.
Importing your existing bug history
In some cases, the Launchpad team can import your existing bug history from another bug tracker. This may mean you can switch to Launchpad's bug tracker without having to maintain your previous bug tracker in a read-only mode.
Get in touch to see if we can help.
Bug supervisors
bug supervisor: handles day to day management and triage
Many projects create specific teams to act as the bug supervisor, allowing several people to triage bugs without gain.
If you'd prefer not to set these - perhaps because your project is small enough not to need specific contacts - you, as project owner, take them by default.
The bug supervisor's role
You may want to give some people extra bug editing privileges: The bug supervisor's role is to manage the planning of bug work and the triage of newly reported bugs.
Launchpad helps them do this by giving them access to:
- target bugs to a milestone
- set the importance of a bug
set certain bug statuses.
To set your project's bug supervisor, visit its bug overview page - for example: https://bugs.launchpad.net/inkscape - then choose the edit link next the the bug supervisor role listed on the page.
Next step
Now you've set up the basics, you're ready to start managing your project's bug reports in Launchpad. However, let's first look at how Launchpad tracks the hottest bugs.
