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

Bug #47555 reported by Sebastien Bacher on 2006-05-30
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

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) wrote :

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.

Changed in malone:
assignee: nobody → bjornt
status: Unconfirmed → Confirmed
Brad Bollenbach (bradb) wrote :

I think this is still broken. Bjorn?

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

Graham Binns (gmb) on 2008-08-06
Changed in malone:
assignee: bjornt → gmb
milestone: none → 2.1.8
status: Confirmed → Triaged
Changed in malone:
milestone: 2.1.8 → 2.1.9

Pushing this off for a cycle.

Changed in malone:
milestone: 2.1.9 → 2.1.10
Graham Binns (gmb) on 2008-10-03
Changed in malone:
milestone: 2.1.10 → 2.1.11
Graham Binns (gmb) wrote :

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

Changed in malone:
importance: Medium → High
Graham Binns (gmb) wrote :

Moving to 2.1.12; no time for it this cycle.

Changed in malone:
milestone: 2.1.11 → 2.1.12
Graham Binns (gmb) wrote :

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.

Changed in malone:
milestone: 2.1.12 → none
Graham Binns (gmb) on 2009-12-11
Changed in malone:
assignee: Graham Binns (gmb) → nobody
Robert Collins (lifeless) wrote :

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.

Changed in malone:
importance: High → Medium
Robert Collins (lifeless) wrote :

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.

summary: - should be possible to change the product of an upstream task
+ when a bugwatch becomes a duplicate to a different upstream project the
+ upstream product in launchpad does not update
Changed in launchpad:
importance: Medium → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers