See a burndown or cumulative flow chart for a particular subset of user stories independent of project hierarchy.
With the 2009.3 release the Reports tab now includes two additional options which will allow you to view the progress of epic stories and their children:

The Story Burndown report will look like a typical burndown chart that has been scoped by your chosen parent story and the data will include each child associated with that parent. Choose a story by typing in case-sensitive text into the search box and select the appropriate story.
By default, the burndown chart will show the historical progress for that epic for the past 30 days. You can use the Start Date field to select a begin date other than the default 30 days.
There are also a couple of additional metrics included with this chart:

The Story Cumulative Flow Diagram is also typical of our current cumulative flow charts and like the Story Burndown, it will let you limit results to a particular epic story and it's children. Story selection works in a similar fashion as well by typing case-sensitive text into the search box and selecting the appropriate story
A couple of items to note:
For additional details and descriptions, please also take a look at the online context sensitive documentation available for each of those reports. You can get there by clicking on the help icon
at the top right of those pages.
Also, since both of these charts are part of the new reporting functionality, we're very interested in customer feedback. Please see the related post on New and Enhanced Reporting and let us know what you think!
Comments
I tried this Story Burndown for one of our EPIC story, and it comes back "No Results found."
Tarun, I created a support case in your name so we can track this issue. I'll contact you directly via email.
Is there any reason for the search box to be case sensitive?
Can this at least be a check box??
Hi Steve,
Great idea! We have a couple of stories in our backlog to address case insensitive searches in our application. I'd encourage you to post this idea in our Feature Request hive. We also want to ensure when we roll out this feature that it is compatible with similar search functionality through the API as well.
-Matt