hard to find closed tasks through the searchTasks() API
Bug #672883 reported by
Alex Chiang
This bug report is a duplicate of:
Bug #613713: Provide a way of fetching all bug_tasks on a project.
Edit
Remove
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Currently, the searchTasks() API will not return bugs in the "Closed" state (Won't Fix, Invalid, Fix Released).
This behavior is not documented in the API documentation here:
https:/
In order to get a list of all bugs, one must do something like the following:
http://
Two launchpad hackers have wondered aloud if this behavior should be a bug.
1) start reading conversation here: http://
2) stray review comment during merge proposal: https:/
Thanks for considering this.
| affects: | launchpad → malone |
Revision history for this message
| Deryck Hodge (deryck) wrote | #1 |
| Changed in malone: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| tags: | added: api doc |
Revision history for this message
| Alex Chiang (achiang) wrote | #2 |
| summary: |
- searchTasks() API should search all bug statuses by default + hard to find closed tasks through the searchTasks() API |
To post a comment you must log in.
I don't think we should change the current behavior because for another class of user including closed bugs would really annoy. We should document the current behavior and perhaps had some convenience parameters or object to make it easier to include closed bugs. For example, if we could understand enums via the api and say status=
Cheers,
deryck