Rightsizing ROI Enhancements - Realized Savings, user experience, & reporting impacts

As a FinOps practitioner responsible for driving FinOps best practice adoption across our organization, and responsible to deliver potential & realized savings metrics to the executives, I require the ability to report on the savings offered & realized on a monthly basis; As well as report on actions taken by our tenants to drive savings.

As such, I request the following product enhancements as they relate to the Rightsizing ROI and the Rightsizing dashboard within Cloudability.

Rightsizing Dashboard:

Include ROI Issue # in Exports from the Rightsizing dashboard. Despite being displayed within the rightsizing dashboard UI, the issue # is not exported. Adding this feature to the export function will allow tenants to track opportunities that exist in the ROAR report.
We would like the ROI issue # added to the rightsizing dashboard filters to allow tenants to search out the opportunity flagged within the ROI policy. When in the rightsizing dashboard, users cannot filter on the ROI issue number. This is required given that the ROI ticket is created at a point in time with a potential savings amount which is never updated again. However, if that opportunity is within 30 days & exists in the rightsizing dashboard, the potential savings amount is updated and adjusted regularly.

Rightsizing ROI

Potential Savings Figure Enhancement: If ROI ticket exists within the rightsizing dashboard within the 30 day window, the potential savings amount should be adjusted in the ROI ticket as it updates in the rightsizing dashboard. The fact that the ROI ticket potential savings figure is never adjusted even when the opportunity is within 30 days and is continuously adjusted in the rightsizing dashboard affects the accuracy of reported potential/realized savings figures . If the functionality to update the savings exists in one cloudability module, it should be extended to other modules.

Provide the ability to update table settings within the rightsizing ROI to pull in various mapped tags and Account group tags similar to the functionality within Insights -> Resource Inventory. This will enhance the end user experience and allow them to filter and export based on mapped CSP tags & account group tags to provide more granular reporting to determine benchmarking and investigation assignment.

Provide consistency across UI and data exports with dimension names. Ex. Ticket is "Ticket" in the ROI table in the UI and in the filter- but in the export & TBM mapping for the ROAR report, the column is simply called "Issue".

Allow comments field to be exported. Bell is using this field to understand why a tenant has indicated the resolution on an ROI is "Won't Do" or "Revisit in Future". This field is not exportable which is not allowing for proper analysis of unactioned opportunities.