Bug status changes to unknown when upstream status changes to dupe
Bug #723274 reported by
j.c.sackett
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
William Grant | ||
Bug Description
Bug 657227 has an upstream task that changed to Unknown for the status when the upstream bug was marked a duplicate. Is this proper behaviour?
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Gavin Panella (allenap) wrote | #1 |
| tags: | added: trivial |
| tags: | added: bugwatch |
| Changed in launchpad: | |
| assignee: | nobody → j.c.sackett (jcsackett) |
| Changed in launchpad: | |
| status: | Triaged → In Progress |
| Changed in launchpad: | |
| assignee: | j.c.sackett (jcsackett) → William Grant (wgrant) |
Revision history for this message
| William Grant (wgrant) wrote | #2 |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| milestone: | none → 11.03 |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I think this is because Launchpad doesn't know what the remote status
"RESOLVED DUPLICATE" means.
Fixing this is probably as easy as updating Bugzilla.
lp.bugs.