The release retrospective report gives good insight to an individual release. I would like to see the same information for a roll-up release. This allows me to understand the delivery of large-scale projects across my organization.
Kole Hainz
Jan 13, 2026
This would be huge. The retrospective report is useful, but it's very time consuming to check for each individual product across a large portfolio. Really hoping there's progress on this soon!
This is a big gap for large companies that utilize Aha! Our releases our fairly complex across multiple workspaces and the retrospective report is a great report, but needs to be aggregated (via roll up release) not just an individual release.
I agree that this would be helpful. The data on this view if very helpful. Yet, many of our Epics/Features are delivered across workspaces (as an ART). Seeing this information in the Aggregate would be incredibly beneficial.
+1 from our perspective. This aggregation is critical to this view being rolled out in larger enterprises where it is essentially to track this sort of information across a wider portfolio
This would be very helpful! Additionally, in that same view I would like to be able to see which workspace each record in the Completed records, Incomplete records, Added records, and Removed records sections belongs to.
Who would benefit? PMO What impact would it make? Team can see Burndown chart for entire development term How should it work? Currently Burndown chart is only available for a release. However, sometimes it is required to see the chart for start to...
Guest
over 2 years ago
in Releases
0
Future consideration
This would be huge. The retrospective report is useful, but it's very time consuming to check for each individual product across a large portfolio. Really hoping there's progress on this soon!
This is a big gap for large companies that utilize Aha! Our releases our fairly complex across multiple workspaces and the retrospective report is a great report, but needs to be aggregated (via roll up release) not just an individual release.
I agree that this would be helpful. The data on this view if very helpful. Yet, many of our Epics/Features are delivered across workspaces (as an ART). Seeing this information in the Aggregate would be incredibly beneficial.
+1 from our perspective.
This aggregation is critical to this view being rolled out in larger enterprises where it is essentially to track this sort of information across a wider portfolio
This would be very helpful! Additionally, in that same view I would like to be able to see which workspace each record in the Completed records, Incomplete records, Added records, and Removed records sections belongs to.