As a developer new to Jaspersoft I'm spending a great deal of time drinking from the firehose trying to learn all the ins-and-outs of a new reporting tool. Something former CA PPM reporting tools have been lacking are good Release Management features for simple, reliable, repeatable promotion of report content from Development to Test to Production environments. Good news here is that Jaspersoft Studio has us covered. If you haven't tried this yet, follow along.

1) In Jaspersoft Studio's Repository Explorer, right click on the folder of the report you wish to migrate and choose Export Metadata.

2) Give your export zip a name and pick a location to export the report unit archive to. For simple promotion of a new report, uncheck all Include 'X' checkboxes then click Finish.

A zip file archive of the Report Unit (report and dependent files) will be created.

Import the Report Unit into a Higher Environment (Promoting).

1) In Repository Explorer expand the first level of folders on the Jaspersoft server you wish to migrate your Report Unit into (this 'activates' the server connection). Right click on the server node and select Import Metadata.

5) In Repository Explorer right click on the Jaspersoft Server you've just imported into and select Refresh.

6) In Repository Explorer expand the folders and inspect the newly imported Report Unit and dependencies. In the example below, although we only selected the Resource Spend folder in step 1 above for export, the whole Report Unit - all the contents of the report folder and report dependencies - were exported into the zip archive and the full folder structure and dependencies were brought into the new environment via the import.

Thanks Eric for following up with the On Demand team. Putting my good steward of Change & Release management hat on - a developer running around with superuser and the ability to migrate between environments isn't always considered a good thing. I'm certain larger On Premise implementations have release teams who would be responsible for promoting content such as this - so working with support via a ticket isn't much different. Does the On Demand support team have a KB article on their process for contacting them & the information they need to migrate reports for customers? If this exists, we could link it here and this could be a one stop 'how to' shop for On Premise and On Demand.

Agreed that a standard procedure for OD team moving report across environments would be greatly appreciated.

As part of a release team that has both new and updated reports to be moved across environment in every sprint, we could really use some help and cut down the time spent on releasing Jaspersoft reports (new and changed)!