'Unknown' is not valid status when using searchTasks() via the API
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
The list of statuses listed here:
https:/
includes 'Unknown', but actually specifying that status causes a
failure:
...
for bug_task in milestone.
File "/usr/lib/
url, in_representation, http_method, extra_headers=
File "/usr/lib/
raise HTTPError(response, content)
lazr.restfulcli
Response headers:
---
connection: close
content-length: 230
content-type: text/plain
date: Tue, 16 Nov 2010 18:30:57 GMT
server: zope.server.http (HTTP)
status: 400
vary: Accept,
via: 1.1 wildcard.
x-powered-by: Zope (www.zope.org), Python (www.python.org)
---
Response body:
---
status: Invalid value "Unknown". Acceptable values are: New, Incomplete (with response), Incomplete (without response), Incomplete, Opinion, Invalid, Won't Fix, Expired, Confirmed, Triaged, In Progress, Fix Committed, Fix Released
---
Notice also that 'Incomplete (with response)' and 'Incomplete (without
response)' are not included in the documentation.
affects: | launchpad → malone |
tags: | added: api documentation |
Changed in malone: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: easy |
summary: |
- 'Unknown' is not valid status when using milestone.searchTasks via the - API + 'Unknown' is not valid status when using searchTasks() via the API |
Changed in bug-repo-syncer: | |
importance: | Undecided → Low |
status: | New → Confirmed |
no longer affects: | bug-repo-syncer |
tags: | added: bug-search |