Bugzilla bug watch status mappings shouldn't default to invalid
Bug #237126 reported by
Graham Binns
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Medium
|
Bryce Harrington |
Bug Description
At present, if we don't understand the status and resolution of a bugzilla bug watch we set the bug watch's status to Invalid (e.g. Bug #237123).
We shouldn't do this. Instead, we should default to Unknown.
Related branches
lp://qastaging/~bryce/launchpad/lp-31745-237126-617102
- Deryck Hodge (community): Approve (code)
- Launchpad code reviewers: Pending requested
-
Diff: 56 lines (+16/-5)2 files modifiedlib/lp/bugs/doc/externalbugtracker-bugzilla.txt (+3/-1)
lib/lp/bugs/externalbugtracker/bugzilla.py (+13/-4)
description: | updated |
Changed in malone: | |
status: | New → Confirmed |
Changed in malone: | |
assignee: | nobody → Graham Binns (gmb) |
Changed in malone: | |
assignee: | Graham Binns (gmb) → nobody |
tags: |
added: qa-untestable removed: qa-needstesting |
Changed in malone: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
same/similar problem showing up in bug #36424 where RESOLVED / WORKSFORME is mapped to Invalid.