Feature Requests

For the 'Forecast Cost' value inside of a Perspective is meaningless. It currently always shows the next 30 days, which is useless when trying to forecast costs for a Single month or For a quarter. What should happen is the Forecast value should respect the Data Range and the Period filters. If you are selecting "This month" and "Daily" it should forecast to the end of "this month". Details: * when Selecting show "this month" the 'forecast cost' value should forecast to the end of "this month". * when selecting show "this year" it should show the forecasted value for the remainder of "this year"

anomalies do not decrease when marked as a false positive, only a message appears but leaves the anomaly in the same list

When setting the report on a quarterly frequency. Currently, only the last month's cost can be provided in the report. This doesn't match the frequency and period needed. UKRI would like to be able to use custom dates such as last 3 months or custom period

Currently you can add CCM Recommendations to the "Ignore List". Requesting the ability to "Snooze" CCM Recommendations. Thus ignoring them for a period of time.

We need some sort of alerting outside of Harness when an autostopping rule fails to restart an instance as scheduled. Harness shows logs when an instance fails to restart, but we need an alert to bring attention to it

Encoded links do not work in Schedule Delivery --> Advanced Options, even after enabling the checkbox Include links

Currently the clone of Read only perspective is not possible. So users can't create a clone and modify the visualisation according to their need.

I've been told that Harness does not have a collective list of feature flags available in the CCM tool. As they are spread across functionality they add them to release docs and corresponding detail section of the documentation. Can a list please be provided with links to these release notes and other relevant descriptors of the flags purpose and function? We are missing out on things we don't know exist and may have just resigned ourselves to not having.

Allow a recommendation to remain as listed once it has been put into a new "In Progress Status". This gives the engineer a chance to return to the tool to register the action taken and provide a fair estimation of the actual savings gained. Sometimes it takes a few weeks before the savings can be seen in enough data to prove the value of the actioned recommendation. A5t the moment the Engineer only has until the next update, when the recommendation may just disappear! Mad!

It appears that the parameters by which Harness moves their Recommendations to "accepted" status is too rigid. It doesn't appear to be observing the ticket's resolution field, and is looking at the status, so anything outside of the actual "Done" status won't be accepted We'd like Harness to either allow us to customize the acceptance criteria, or broaden the range.