| 2010-02-01 06:44:58 |
Graham Binns |
description |
When Launchpad adds a link upstream, it should only be for the bugs currently selected in the upstream bug tasks.
On upstream bug https://bugzilla.mozilla.org/show_bug.cgi?id=499233
which is the upstream for bug 398128, Launchpad also added bug 195698 since it's considered an "Upstream Bug Watch". That however is incorrect as bug 195698 is upstream bug
https://bugzilla.mozilla.org/show_bug.cgi?id=356097 which is similar, but not the same. |
What happens:
If a bug has a bug watch against an upstream bug, even if that upstream bug has nothing to do with the actual bug, Launchpad will still sync comments for that bug watch and add a back link, where possible.
For example, bug 454166 was fixed by a change to a package and the changelog was posted to the bug as a comment by the LP Janitor. This comment contained the URL of an upstream bug, so a bug watch was created for that upstream bug.
Checkwatches then imported the comments from that upstream bug, even though the upstream bug had nothing to with the Launchpad bug. (see http://paste.ubuntu.com/333331/ for the resulting bugspam).
Also, complaints have been made upstream about the automatic back-links that Launchpad makes. If an bug is mentioned in a Launchpad bug comment and thus has a watch generated for it that watch will then be linked back to the upstream bug, even if it's not even tangentially related to the Launchpad bug in question.
What should happen:
Checkwatches should only sync comments and backlink when a bug watch is actually linked to a BugTask. That will eliminate this problem (unless someone adds a nonsensical BugWatch to a BugTask, but we can't prevent users from doing odd things all the time). |
|
