Comment 17 for bug 174404

I'd add a new use case: offline bug processing.

For example today I will be for 2 hours in the train, and I'd like to work on open bugs. In the current situation I need to copy/paste from the website, or make screenshots. And luckily my project has few enough bugs (20) that it all fits on one page, if pagination was involved (like for the Firefox bugs example in the OP) this task would be impossible to perform.

Is this feature such a complex one? Isn't it just duplicating the algorithm used to produce the "+bugs-text" flavor, and add comma's and other info from the database?

I'd be happy to have a look at the code if someone could point me to where the code is generating "+bugs-text".

If we absolutely want to go the API route, I'd have to create an external site that queries LP and provides a "download as .csv" option. Seems a better approach to be able to merge that code back into LP instead of having to build yet another external service from scratch.