Remote bugs that are duplicates are shown as "Invalid"

The two options we've got here are:

1. change the bug number in the existing watch
2. create a new watch for the new bug number. Perhaps attach this watch to the task instead of the old one.

It isn't that uncommon for an upstream bug to be marked as a duplicate and then unduped (or marked a duplicate a second time against a different bug).

kiko, should this bug be pretty high priority? For example:

  https://launchpad.net/distros/ubuntu/+bug/50039

It looks like upstream "Rejected" a critical data loss bug, but it was really just duped.

Bumping this to 1.1.10 due to lack of time this cycle.

Untargeting this for now to help with planning. Will retarget it later.

On a related note, if the upstream dupe has a bug in lauchpad as well, it would be nice to do something with that. Tag it likely-dup or something.

Also related, and somewhat more worrisome: Updater has the status on Bug #156689 (https://bugs.launchpad.net/mythtv/+bug/156689) as "Confirmed," when upstream is actually listed as "closed defect: duplicate."

At least with "rejected", someone on launchpad could check and see what is up. With it incorrectly showing confirmed, someone might sit there for a LONG time waiting on upstream action.

Bug activity
Date Who What changed Old value New value Message
24 Oct 07 14:39 Mark Duncan bug added bug
24 Oct 07 16:59 Mark Duncan bug added attachment 'ps3 garbled text.jpg' (Garbled text)
30 Oct 07 09:32 David Morris bug assigned to mythtv
30 Oct 07 11:28 Bug Watch Updater mythtv: status Unknown New
05 Nov 07 23:42 David Morris mythbuntu: importance Undecided Low
05 Nov 07 23:42 David Morris mythbuntu: status New Confirmed
17 Dec 07 20:53 Mario Limonciello mythbuntu: status Confirmed Triaged
01 Jan 08 10:33 Bug Watch Updater mythtv: status New Fix Released
01 Jan 08 19:29 Mario Limonciello bug assigned to mythtv (Ubuntu)
02 Jan 08 10:46 Bug Watch Updater mythtv: status Fix Released New
03 Jan 08 11:17 Bug Watch Updater mythtv: status New Confirmed <--- different mythtv than the ones below I think!
13 Jan 08 16:13 Mario Limonciello mythtv: status New Fix Committed
21 Jan 08 21:00 Launchpad Janitor mythtv: status Fix Committed Fix Released

> Untargeting this for now to help with planning. Will retarget it later.
@Björn: After a year, and subequently after 3 years of an open bug, can you please estimate a date when a decision will be taken about this issue?

It just happened to bug #197028 with bug-watch-updater. Its status is Resolved/Duplicate. Old gnome link:
http://bugzilla.gnome.org/show_bug.cgi?id=347231
( I re-targetted it manually to http://bugzilla.gnome.org/show_bug.cgi?id=103753 )

The "Invalid" status makes users to jump to wrong conclusions, as mentioned above in the comments.

I would suggest to just set it back to "Unknown" for now. It seems much more appropriate than "Invalid", until you figure out how to transform the data (whether or not the team intends to fix it that is).

P.S. Forgot to mention that bug #197028 shows the correct status "Resolved Duplicate" on the launchpad menu on the right side.

We might want to keep the original bug watch but dereference on each update - that way if its unduplicated we'll not have lost the correct thing to watch.

+1 and amen to comment #9. If that is not feasible, then at least prefer "Unknown" over "Invalid", as suggested in comment #7.

(Dropping priority as its currently a backlogged item and not queued for anyone to work on).