We have 10 Jira projects that are all working on common versions, sprints, etc. All of our sprints start / stop on the same date, etc. When we release a new version of our product, we ship to the customer the results of 6-8 sprints worth of work in 1 deliverable from all of 10 of these Jira projects.

Currently there is no way to get "rolled up" burn down graphs for the common Jira versions these separate projects are working on. It would be great if:

1. At a minimum, I could get access to the raw data that is used to draw the burn down / burn up graphs for both released and unreleased versions so I could draw my own consolidated "master release" graphs from all 10 projects. Could you expose the data as XLS or CSV files in some directory on the Jira server or expose links so I can save them as needed to disk and then load them into excel and do a roll up graph?
2. Even better (but I'll settle for #1), could I tell Greenhopper the list of Jira projects it should consider when drawing a consolidated release charts? I would name all of my versions the same across all projects so that the roll up can make sense of the data.

This would be very useful - without it the only release planning we can do is on a project by project basis, and not for a master project.