The Bugzilla ExternalSystem should know more about possible resolutions

Bug #31745 reported by Björn Tillenius
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Bryce Harrington

Bug Description

Currently, when updating bug watches, the Bugzilla ExternalSystem sets the status to Rejected, if there is a resolution, and it's not FIXED. We should look at the different Bugzilla instances we update from, and see what kind of different resolutions they use, in order to provide a better status mapping.

We probably will end up with having special handling for each Bugzilla instance, but to begin with we should have reasonable defaults.

Related branches

Revision history for this message
James Henstridge (jamesh) wrote :

Here is a short summary of what we are watching right now:

Standard Bugzilla:
  Statuses:
    UNCONFIRMED, NEW, ASSIGNED, REOPENED, RESOLVED, VERIFIED, CLOSED
  Resolutions:
    FIXED, INVALID, WONTFIX, LATER, REMIND, DUPLICATE, WORKSFORME, MOVED

Freedesktop.org:
  Custom statuses:
    NEEDINFO, PLEASETEST
  Custom resolutions:
    NOTABUG, NOTOURBUG

Gentoo:
  Custom resolutions:
    CANTFIX, NEEDINFO, TEST-REQUEST, UPSTREAM

Gnome.org:
  Custom statuses:
    NEEDINFO
  Custom resolutions:
    NOABUG, NOTGNOME, INCOMPLETE, GNOME1.x, OBSOLETE, NOTXIMIAN

Kernel.org:
  Custom statuses:
    REJECTED, DEFERRED
  Custom resolutions:
    CODE_FIX, PATCH_ALREADY_AVAILABLE, WILL_NOT_FIX, WILL_FIX_LATER, UNREPRODUCIBLE, DOCUMENTED, INSUFFICIENT_DATA

Mozilla.org:
  Custom resolutions:
    EXPIRED

Novell:
  Defaults

Samba:
  Defaults

sourceware.org:
  Custom statuses:
    SUSPENDED, WAITING

Christian Reis (kiko)
Changed in launchpad:
assignee: nobody → bjornt
status: Unconfirmed → Confirmed
Changed in malone:
assignee: Björn Tillenius (bjornt) → nobody
Revision history for this message
Bryce Harrington (bryce) wrote :

(I suspect this is not a super critical issue, but I've just finished a branch that worked on this section of the code so it was calling to me.)

For the most part, most of those statuses are mapped. Of the remainder, I suspect some like fdo's "PLEASETEST" are not heavily used. But anyway here's a patch to add them.

I omitted statuses that looked to me like they'd map to Invalid since that's the default anyway. I also added some mappings to Expired since we have that resolution in launchpad now.

The other branch I mentioned should probably land before this fix can go in, since this one will conflict with that one.

Revision history for this message
Bryce Harrington (bryce) wrote :
Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Bug fixed by a commit
Changed in malone:
assignee: nobody → Bryce Harrington (bryceharrington)
milestone: none → 10.09
tags: added: qa-needstesting
Changed in malone:
status: Triaged → Fix Committed
Bryce Harrington (bryce)
tags: added: qa-untestable
removed: qa-needstesting
Revision history for this message
Bryce Harrington (bryce) wrote :

I've done enough local testing that I'm confident this is fixed in the codebase, however I've not been able to verify it on staging. The change carries little risk of causing other problems; worst case is the issue still remains unfixed.

Curtis Hovey (sinzui)
Changed in malone:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.