Comment 2 for bug 333215

This is making Ubuntu's upstreams unhappy. Even when a project has explicitly told Launchpad where they track their bugs, they're still finding that some bugs are being reported against their project in Launchpad.

This gives the upstreams the impression that we're ignoring their preferences and also that we're leading bug reporters down dead-ends.

Following a complaint from an upstream about this, I tried the following in staging:

Selected a random bug and marked it as "Also affecting" Pitivi. LP did the right thing and told me that Pitivi uses the Gnome Bugzilla. However, it then gave me this option:

"I just want to register that it is upstream right now; I don't have any way to link it."

We should explicitly state on the bug report that this bugtask is, in effect, useless. Actually, I'd question the usefulness of this option. What does it give us, other than a list of bugs against a project that doesn't use LP? It risks alienating upstreams by making it appear that we're inviting people to report bugs against their project, even when they've told us they use an external bug tracker, and it gives the reporter the impression of having done something when really they have, as far as I can see, achieved nothing useful.

Beneath that, it said:

"There is no bug supervisor for PiTiVi. This means that there is nobody upstream we can notify about this issue."

That's not much help and not strictly true. The project has a maintainer and so LP should fall-back to the maintainer if there's no bug supervisor.

I can't see any circumstances in which it should be possible to report a bug in LP's bug tracker against a project that does not use LP's bug tracker, *unless* LP's bug tracker is somehow a front-end for the upstream's bug tracker.