Feature Requests

Recommendations workflow is clunky where I: Filter a list of recommendations that is unique to my group/platform-> Click into a recommendation-> recommendation appears within the page instead of a new tab -> I gather the recommendation then I must go back to the results filtering page to click on another recommendation. Can I suggest to open a new tab everytime I click into a recommendation. So I can preserve the filtered list whilst still being able to collate all the recommendations I need

Please enable the Budget Group feature for our Harness CCM account. This feature was noted as being "behind a feature flag CCM_BUDGET_CASCADES" and only Harness support could enable it for our organization. Let me know if there is any additional information needed to proceed. Thanks, Megan Faykosh

The "Potential monthly spend" column in Open and Ignored recommendations is confusing. The data shows the Current Spend. To my mind a potential spend is what you would spend after a change (logically in this recommendations page - after you implement the recommended change). Please consider changing the data shown, changing the column heading or adding a column to show the new spend you'll achieve if you make the recommended change. I would name it "Potential Monthly spend" but that heading is taken.

As discussed with the Harness team - Hitesh, Karan, Max - at FinOps X 2026 I am submitting a PFR request for a connector integration with OCI. The primary use case is to pull down the Oracle Exadata CUR with daily cost usage. Sharing details and summaries from our discussion. Please clarify anything I misspoke here. Knowns: -Per Harness team, currently supported FOCUS spec is v1.1. No other FOCUS spec is supported. -Per Oracle Billing team, Exadata CUR is available GA w/ v1.0 and has a private preview for v1.3. Unknowns: FOCUS backwards compatibility v1.1 -> v1.0 Next Steps: ELVH placed a ticket with Oracle to understand CUR FOCUS spec availability from OCI. Harness team to share further details/reqs on developing the integration with OCI billing data

My request is that the information that anomaly is caused due to marketplace purchase is not been sent in Anomaly notification. What we are looking is Anomaly notification should have specified this cost is from AWS MarketPlace in the details. Why is this information do not have it in email notification and what need to be done to add these details in the email notification ?. We opened support request #115738 and they notified to open a Feature request.

Support for OCI should be added to Cloud Cost Management.

We'd like the ability to create sub-folders for Perspectives to keep them organized. Currently with over 500 Perspectives and growing, only having the one layer of folders does not allow for proper management of Perspectives.

Problem: Currently, GCP folder names (available as "Ancestor Display Name" in Dashboards) are missing as a dimension when defining Cost Categories. Impact: Customers lwho have mature GCP folder structures but inconsistent project naming or tagging are unable to effectively group costs using their existing organizational hierarchy. Requirement: Expose "Ancestor Display Name" or "Folder" as a selectable field in the rules engine for Cost Categories, similar to how it is currently available for Dashboards.

Wanted to create the dashboard for policy and Governance therefore need the ability for this

Please add the capability for Autostopping to control Azure VMScaleSets.