Bulk save to pdf

PROBLEM STATEMENT:

Each of our projects (initiatives) contains a large amount of content. We need a fast and easy way to capture all of the content related to a project for version control/snapshot, auditing purposes, as well as printing out to read offline. 

We are looking to have high-level overview of the project followed by details of each Master Feature followed by details of each Feature related to that Master Feature. We need an easy and reusable method regardless of what contents we want to include. It should be easy to update as the content related to the initiative changes, and it should also be easy to "repeat" for another initiative once it is set up. Once you set it up for one initiative you could simply change the name of the initiative and save the "job.

A recent example has 52 master features and 125 features. Because of the 40 page limitation in notebooks, we are unable to make each of these items a page in the notebook. If we make reports and then place those reports into the notebook, that is a large amount of manual effort.

To be an acceptable solution, it should take 10 mins or less to get the content I need out of Aha. If it takes me an hour to make dozens of reports and put them into a notebook or go to every feature and master feature to add it one-by-one to the notebook, that is not a solution that will work for us. 

IDEA:

We would like to be able to bulk select features and master features, and then send those all to a pdf with each item starting on a new page.

At a very minimum, that might be something like creating a list of features, and bulk sending them to pdf. Then repeating the same process for master features. This would be a very quick and rough way to do it that wouldn't be pretty. I worry that it would just look like someone printed off a bunch of webpages with no rhyme, reason, or organization to them. 

A better way might be to allow us to print from a hierachy report, where the content of each object gets placed on a new page of the pdf, and the pages are built by working down the hierarchy report left to right, top to bottom. In fact, if the hierarchy report was placed at the beginning of this document, it could function as a table of contents.

For example: If I have a hierarchy report showing Master Features and Features, then I would expect the pdf that I generate to have the whole hierarchy report on page 1, then the first Master Feature on page 2, then each of the Features contained by that Master Feature on the following pages (starting with a new page each time). Then the second Master Feature would be printed, followed by its Features, then the third Master Feature, followed by its Features, etc. 

Since the master features and features are related in Aha, we would like the output to show that relationship, or at least group content logically.