when a bugwatch becomes a duplicate to a different upstream project the upstream product in launchpad does not update

[Sebastien Bacher]

example: https://launchpad.net/distros/ubuntu/+source/gtk+2.0/+bug/47399/+index

* forward a bug on gedit
* open an upstream task for it
* notice it's a dup of a GTK issue
* mark the upstream bug as duplicated
* try to make understand to launchpad that the upstream has moved now...

The example has an user comment about that by example, it's confusing for people

[Christian Reis (kiko)]

I believe this is already fixed and will be rolled out to production next week -- it falls out of the improved BugWatches work Bjorn did.

[Brad Bollenbach (bradb)]

I think this is still broken. Bjorn?

[Björn Tillenius (bjornt)]

On Tue, Aug 29, 2006 at 10:27:57PM -0000, Brad Bollenbach wrote:
> I think this is still broken. Bjorn?

Yes, the bug is still not fixed. It's slightly better now, though,
since you can reject the task and create a new one with the correct
product.

[Graham Binns (gmb)]

Pushing this off for a cycle.

[Graham Binns (gmb)]

Bumping this up a priority level based on a request from the Jorge.

[Graham Binns (gmb)]

Moving to 2.1.12; no time for it this cycle.

[Graham Binns (gmb)]

Untargeting this for the time being. It didn't land in 2.1.12 and I don't know if I'll have time to fix it in 2.2.1.

[Robert Collins (lifeless)]

Putting the priority back - its a shame we didn't get to it, but its not the immediate set of major things to fix in bugs, and while annoying there is an existing workaround.

[Robert Collins (lifeless)]

I've tried to capture this a little better in the subject, and reflecting that its not in the current set of scheduled works have set the priority to low.