Insights & Reporting

We have several repositories for different platforms in our project. We follow them in CircleCI. It's very important for us to have opportunity to see health status for all projects in one place fast and without extra actions. It seems that INSIGHTS has to be a good candidate for that. According to a new deploying strategy we've changed a default branch for one of our repository in Github project settings. Previously we used 'master' as a default branch but now we use 'alpha' branch. Unfortunately CircleCI INSIGHTS hasn't inherited that change and still shows master statistics by default. So now we have to go inside repository details from INSIGHTS panel and switch branche to see 'alpha' branch state. It's uncomfrotable. There should be a way to change that! CCI-I-414

While the Insights API is nice, it's great to be able to point team members at a visual tool. CCI-I-1520

Hi,We have a monorepo for our front end. After putting it on CI as a workflow with multiple jobs involved, it shows a green project status however the workflow as a whole is failed. My guess is that's happening because the insights screen shows the status of the build instead of the status of a workflow. Is there a way to display a status of the workflow on the Insights screen?Thanks. CCI-I-146

While looking to see if anyone had requested this, I found a support request that someone had created talking about it, but no actual submission. In Circle v2, developers can create workflows of different steps. Steps have different purposes and can take vastly different amounts of time. Each step of a workflow generates a separate build as the workflow is run. However, inside insights, it's impossible to distinguish between the different types of step in a workflow, and therefore averages like "Median" become useless as a measure of build health. The insights product should recognise workflow builds, and provide separate metrics (and possibly separate graphs) for each step. CCI-I-876