launchpad help|
Size: 2406
Comment:
|
Size: 2412
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| The top two rows don't have a "person" assigned to fix them. Instead, they link to bugs in external trackers, because those two rows refer to communities outside of Launchpad. The status of the rows is determined by looking at the external bug tracker, and reading the status of that bug in the relevant tracker. |
The top two rows don't have a "person" assigned to fix them. Instead, because they refer to instances of the bug in external communities, they have a link to that bug as reported in the bug trackers used by those communities. Launchpad determines the external bug's status by regularly checking the relevant tracker. |
| Line 15: | Line 13: |
| If you mouse over those two links in the "assignee" column you will see that they are links to those bugs in the bug trackers for SUN Java and Debian respectively: | Mouse over those two links in the "assignee" column and you will see URLs for the SUN Java and Debian bug trackers respectively: |
| Line 20: | Line 18: |
| This is one of the unique features of Launchpad. It can support such links to bug trackers that are running Bugzilla, RoundUp, Sourceforge or the Debian BTS. We will add support for additional trackers as needed to facilitate collaboration across the free software projects that use them. This means that projects can leverage the benefits of Launchpad without giving up their own bug tracker if they prefer to use their own hosted infrastructure. In some cases, we import ALL the bugs in a project bug tracker into Launchpad automatically, because there are other communities that want to be able to link to them trivially. In other cases, those links are just created on demand. | This is one of the unique features of Launchpad. It allows you to track the status of bugs in external trackers that run Bugzilla, RoundUp, Sourceforge or the Debian BTS. We will add support for additional trackers, when that becomes necessary to facilitate collaboration across the free software projects that use them. |
| Line 22: | Line 20: |
| We call such a link a "Bug Watch" and you can create them for any bug in Launchpad. When you are telling Launchpad about a bug that affects another community, you can supply a URL to the bug report in that community, and the Bug Watch will automatically be created. Once created, Launchpad will continue to monitor that remote bug report automatically and will notify anyone subscribed to the Launchpad bug when the remote bug changes status. | This means that projects can leverage the benefits of Launchpad without giving up their own bug tracker, if they prefer to use their own hosted infrastructure. In some cases, we import ALL the bugs in a project bug tracker into Launchpad automatically, because there are other communities that want to be able to link to them trivially. In other cases, project members can create those links when they need them. We call such a link a "Bug Watch" and you can create them for any bug in Launchpad. When you are telling Launchpad about a bug that affects another community, simply provide the external bug report's URL and Launchpad will automatically create the bug watch. Once created, Launchpad will monitor the remote bug report automatically and notify subscribers to the Launchpad bug of any changes to the status of the remote bug. |
Monitoring bugs in other bug trackers
Look at the "assignee" column for [https://launchpad.net/bugs/86103 bug #86103] again:
attachment:multiprojectbugs.png
The top two rows don't have a "person" assigned to fix them. Instead, because they refer to instances of the bug in external communities, they have a link to that bug as reported in the bug trackers used by those communities. Launchpad determines the external bug's status by regularly checking the relevant tracker.
Open up the bug in a new tab in your browser using this link, so you can interact with it more directly:
Mouse over those two links in the "assignee" column and you will see URLs for the SUN Java and Debian bug trackers respectively:
This is one of the unique features of Launchpad. It allows you to track the status of bugs in external trackers that run Bugzilla, RoundUp, Sourceforge or the Debian BTS. We will add support for additional trackers, when that becomes necessary to facilitate collaboration across the free software projects that use them.
This means that projects can leverage the benefits of Launchpad without giving up their own bug tracker, if they prefer to use their own hosted infrastructure. In some cases, we import ALL the bugs in a project bug tracker into Launchpad automatically, because there are other communities that want to be able to link to them trivially. In other cases, project members can create those links when they need them.
We call such a link a "Bug Watch" and you can create them for any bug in Launchpad. When you are telling Launchpad about a bug that affects another community, simply provide the external bug report's URL and Launchpad will automatically create the bug watch.
Once created, Launchpad will monitor the remote bug report automatically and notify subscribers to the Launchpad bug of any changes to the status of the remote bug.
Now, look a bit further down the page for [https://launchpad.net/bugs/86103 Bug #86103]. See how each of the comments on the bug looks like it is an email? That's because Launchpad's bug tracker allows you to interact with it completely via email. That's the next stop on our tour: [:ReviewersGuide/BugsByEmail:the bug tracker email interface].
