When looking into failed tests from the Top 10 list, I want to be able to drill down into the samples of the failures. As it works now, I have to go click through all failed runs to find one that contains the failed flaky test that I'm investigating. If the test is failing 40% of the time, then I've got a 4 in 10 chance of finding that failure by browsing through failed runs.

So CircleCI Insights's dashboard shows "Median Queue Time" -- but: does not show what is the period over which that "median queue time" was calculated (was that over the past hour? past day? past week?), and does not give me the ability to configure CircleCi Insights's to calculate this over a different period (maybe I want to see over the past 2 weeks the median queue time... It would be great if Datadog has that "median queue time" so I could graph that information as well as set up warning and alert thresholds. I could also use: "maximum queue time" so that I could monitor the longest a test execution has had to wait for a container -- for instance, if the maximum queue time measured over the past 60 minutes shows that one job had to wait 5 minutes for a container...maybe it's time for another container "current queue depth" -- for instance, if the queue reaches 5...maybe it's time for another container Thank you for your assistance! CCI-I-1135

My team is integrating performance metrics into the build and we would like the ability to have a job with a status of warning that turns yellow instead of just having the success/fail statuses so that we can warn developers when performance metrics are getting close to thresholds.

I would like the ability to customize the date ranges for your insights tab. Essentially, the week, 30 day, 60, and 90 day options can be limiting.

The current time window only allows us to select "last -- days". Instead, it'd be nice if we can select the time such as "from May 1st, 2023" to "to May 31, 2023".

In teams that rely heavily on Insights to understand their productivity and success metrics, canceled builds should not count as a failed build as this throws off the metrics used by a team.

It would be helpful if the flaky test information in Insights also included: A link to when the test first became flaky The ability to see flaky test information from a customized time period

Currently, to find a test, a user needs to manually click through runs to locate a test. For tests that fail often, they are easy to find. For tests with infrequent failures or any updates that engineers need to evaluate, it is difficult to locate the test without a search functionality for the test name itself.

In some cases, approval gates are used for rollbacks or circumstantial deployments. As an option, if all jobs prior to the approval are successful, then the workflow should be considered successful.

Add monthly credit consumption data as a graph on Insights. Currently you need to check Usage page and click on each month to get the usage data. It'd be great to have usage history graph instead.