RELATED IDEAS
Allow nesting of rollup releases
Rollup releases are very useful in organizations with complex and nested product lines and products. A top level product may have a V2.0 which is a rollup of three subsystems, a perfect use case of a rollup release. If each of the subsystems, in turn, has sub-sub-systems with releases that need to be rolled up, they would benefit from having their own rollup releases. If the highest level rollup release could contain rollup releases below it, this would really add value.
An alternate implementation would be to allow any one product release to belong to more than one Rollup release. Today, a product workspace release can only belong to one rollup, which is not workable in the scenario where the product release is a member of the rollup release of its product line and also a member of a rollup release higher in the overall system hierarchy.
This is exactly what we need and it would provide value to anyone with a large portfolio.
This is close enough to what I was coming here to say. Basically, let me click on one of the organizational units and get as many different views automatically "rolled up" as possible. I don't want reports that I have to create, just the ability to click on an Org/Team/Category name and get a view of everything under it.
This would really add value as we roll out Aha!