Comment 2 for bug 613713

Sure. This is for the gcc-linaro project and some of the bugs against
this project will be used to track upstream status.

For example, a bug is reported against Linaro GCC, fixed there, marked
as affecting the Linaro GCC Tracking project, and then this tracking
ticket is used to track the upstream patch status.

This means that I need all bugs in all states so that I can check bzr
commit revisions against the tracking tickets.

I can imagine getting up to hundreds of bugs.

-- Michael

On Thu, Aug 5, 2010 at 4:34 PM, Robert Collins
<email address hidden> wrote:
> The all_bugtasks collection provides this. I'm not sure why its exported
> in the first instance.
> However, these collections are _huge_ - hundreds of thousands of
> entries, and I'm extremely dubious about the value, and concerned about
> the cost, of exporting them.
> Can you give more information on your use case?
> ** Changed in: malone
>       Status: New => Incomplete
> --
> Provide a way of fetching all bug_tasks on a project
> You received this bug notification because you are a direct subscriber
> of the bug.
> Status in Launchpad Bugs: Incomplete
> Bug description:
> I'd like to get a list of all bug_tasks, either open or closed, on a project.
> project.searchTasks(status=...) is OK, but only if all possible values of status are provided somewhere.
> I currently use 'all = "New, Incomplete (with response), Incomplete (without response), Incomplete, Opinion, Invalid, Won't Fix, Expired, Confirmed, Triaged, In Progress, Fix Committed, Fix Released".split(', ')
> in my own code but that's fragile.
> To unsubscribe from this bug, go to: