Problem:
Greenhopper's burn down chart treats the entire project as a single engineering unit. In reality, most modern systems are composed of several components, each of which has its own unique technology, resources and velocity.

Request:
allow admins to configure burn down chart by component. If component is chosen, the burn down chart will calculate the backlog for that component based on total number of story points. Then, as stories are scheduled to sprints, calculate velocity and burn down rate for each component. Lastly, aggregate all component burn down charts into a integrated chart which displays component burn down within the larger project's burn down.

Benefit:
allows team leads for each component to adjust resources and balance load so that product development proceeds at a unified rate.