bugzilla.kernel.org bugwatch shows wrong status
Bug #177230 reported by
Brian Murray
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Invalid
|
High
|
Unassigned |
Bug Description
The upstream bug watch for bug 84603 shows it being in a status of Confirmed yet actually visiting the upstreams bug web page reveals that the bug is actually new. Looking at the activity log it seems to have changed in July. I wonder if other kernel bugs are affected to or what the cause is.
Changed in malone: | |
importance: | Undecided → High |
status: | New → Confirmed |
To post a comment you must log in.
I think there's some confusion here. If you look at http:// bugzilla. kernel. org/page. cgi?id= fields. html#status you'll notice that NEW is actually Bugzilla's way of saying the bug is Confirmed. Bugzilla has an Unconfirmed status (which we map to New in Launchpad). This is one of the unfortunate consequences of our renaming of statuses, but the way it works is:
- Bugzilla UNCONFIRMED -> Launchpad New
- Bugzilla NEW -> Launchpad Confirmed
Annoying, huh?