Launchpad itself

Doesn't show importance of watches on remote bugzilla bugs from freedesktop.org

Bug #389269 reported by Bryce Harrington on 2009-06-19

This bug report is a duplicate of: Bug #176906: Display imported Bugzilla Severity field (instead of Unknown). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Launchpad itself	Confirmed	Undecided	Unassigned

Bug Description

Bug watches from launchpad to the freedesktop.org bugzilla do not appear to be retrieving the upstream importance values. Several examples:

Priority LP# FDO# FDO-Priority
High 351756 21190 UNKNOWN
High 351756 21571 UNKNOWN
High 356850 21572 UNKNOWN
High 363305 21574 UNKNOWN
Medium 352207 21576 UNKNOWN
Medium 380265 22187 UNKNOWN
Low 338259 21516 UNKNOWN
Low 353763 19174 UNKNOWN
Low 353763 21577 UNKNOWN
Low 363174 21579 UNKNOWN

I'm looking at writing a report tool for Rick Spencer to display the current status and priority of bugs we've upstreamed to Intel, so not being able to see what the upstream bug priority is through the launchpad api is needed.

Tags:

Revision history for this message

Bryce Harrington (bryce) wrote on 2009-06-19:

Fwiw, I've also tried using the watch.remote_status field from the launchpad api.

Revision history for this message

Bryce Harrington (bryce) wrote on 2009-06-19:

Meanwhile, using this script to workaround the problem:

#!/usr/bin/perl

use WWW::Bugzilla;
use Data::Dumper;

my $bz = WWW::Bugzilla->new(
   server => 'bugs.freedesktop.org',
   email => '<email address hidden>',
   password => '***',
   bug_number => 21190);

printf("%-7s %-9s %-9s\n", $bz->bug_number, $bz->priority, $bz->severity);

William Grant (wgrant) on 2009-07-14

affects:

launchpad → malone

Diogo Matsubara (matsubara) on 2009-07-14

tags:

added: bugwatch

Revision history for this message

Graham Binns (gmb) wrote on 2009-07-15:

Around the time this bug was filed, the freedesktop.org Bugzilla was giving us 500 errors and refusing connections a lot. That appears to now have been resolved and these bug watches appear to have updated correctly.