launchpad help|
⇤ ← Revision 1 as of 2008-05-20 14:05:21
Size: 1647
Comment:
|
Size: 2222
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| Launchpad is unique in that it can track how the same bug affects different communities, such as free software projects or Linux distributions. | As we saw in the [:Bugs/YourProject:introduction] to the bugs section of this user guide, Launchpad's bug tracker is special. |
| Line 9: | Line 9: |
| Each community shares the same: | Launchpad can track how the same bug affects different communities, such as free software projects or Linux distributions. |
| Line 11: | Line 11: |
| * bug number * bug report * comment history. |
Each community shares the same bug number, report and comment history. However, they can keep track of how the bug affects them and how they plan to deal with it by setting their own [:Bugs/Statuses:status], importance and assignee for each bug. |
| Line 15: | Line 13: |
| However, each community can keep track of how the bug affects them and how they plan to deal with it by setting their own: * [:Bugs/Statuses:status] * importance * assignee. This is ideal for free software projects who rely on code maintained by other communities. For example: an Ubuntu user may report a bug in the Exaile media player. Both the Ubuntu packager of Exaile and the upstream Exaile project have an interest in fixing the bug and working together. Launchpad helps them to share their progress through the comment history and email notifications. |
In effect, those communities come together and form an ad-hoc community around the bug report. This is ideal for free software projects who rely on code maintained by other communities. |
| Line 27: | Line 17: |
| There's a table at the top of each bug report in Launchpad that tells you which communities are tracking that bug. | Bugs affecting more than one community is a natural part of life in the free software world. That's why Launchpad makes handling multi-project bugs natural and effortless. |
| Line 29: | Line 19: |
| If you discover that a bug reported in Launchpad also affects your project, you can tell Launchpad using the link directly below the table. | At the top of each bug report in Launchpad is a table that shows you which communities are tracking that bug. |
| Line 31: | Line 21: |
| ||<tablestyle="font-size: 0.8em; width:30%; background:#F1F1ED; margin: 1em 1em 1em 0;" style="padding:0.5em;">attachment:bug-table.png|| ||<style="text-align: center;">'''A bug that affects many projects'''|| |
||<tablestyle="font-size: 0.8em; background:#F1F1ED; margin: 1em 1em 1em 0;" style="padding:0.5em;">attachment:bug-table.png|| To tell Launchpad that the bug also affects your project, use the link directly below the table. It's a simple as that. Now that Launchpad know you also want to track that bug, it shows up just like any other bug reported against your project. The difference is that the bug has become much shallower than if your bug tracker treated your project like an island. It's not just people interested in your project who are looking for a fix, it's people from every project that's tracking the bug in Launchpad! Now that you've marked the bug as also affecting your project, it will show up just like any of your project's bug reports. However, you'll also When you've marked the bug as affecting your project, it will show up in your |
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.
Overview
As we saw in the [:Bugs/YourProject:introduction] to the bugs section of this user guide, Launchpad's bug tracker is special.
Launchpad can track how the same bug affects different communities, such as free software projects or Linux distributions.
Each community shares the same bug number, report and comment history. However, they can keep track of how the bug affects them and how they plan to deal with it by setting their own [:Bugs/Statuses:status], importance and assignee for each bug.
In effect, those communities come together and form an ad-hoc community around the bug report. This is ideal for free software projects who rely on code maintained by other communities.
Working with multi-project bugs
Bugs affecting more than one community is a natural part of life in the free software world. That's why Launchpad makes handling multi-project bugs natural and effortless.
At the top of each bug report in Launchpad is a table that shows you which communities are tracking that bug.
attachment:bug-table.png |
To tell Launchpad that the bug also affects your project, use the link directly below the table. It's a simple as that.
Now that Launchpad know you also want to track that bug, it shows up just like any other bug reported against your project. The difference is that the bug has become much shallower than if your bug tracker treated your project like an island. It's not just people interested in your project who are looking for a fix, it's people from every project that's tracking the bug in Launchpad!
Now that you've marked the bug as also affecting your project, it will show up just like any of your project's bug reports.
However, you'll also
When you've marked the bug as affecting your project, it will show up in your
