Show insights by project and not only by the branch

Lately, the "Insights" show us the frequency that a test breaks in a branch in our repo. But this information is not sufficient for us, so it would be great if there was a way that Insights showed what tests were broken by project and not only by branches.

  • Ana Vale
  • Feb 14 2018
  • Taking votes
  • Attach files
  • Erin Stanfill commented
    28 Jan 19:08

    +1 this.
    I really want to see failed tests insights at the project level. Flaky tests in PRs delay delivery and having insight into which tests need attention would allow me to advocate for spending time fixing specific tests.

  • Kunal Jain commented
    July 02, 2019 23:31

    Thank you so much for your feedback. Internally, we have discussed to provide this data at different levels eg. organization or project.

    Would any of you be interested in doing a formal user interview with us? It is 45 min video call to capture feedback around metrics that you are expecting out of a CI tool. If you are interested, please fill this survey.

    Thank you so much!

  • Adam Dullenty commented
    June 18, 2019 08:08

    +1 - it would definitely be more useful to see insights rolled up to the project level rather than being forgotten about at the individual branch level.

  • Tom King commented
    February 27, 2019 23:59

    +1, the default slicing of builds by branch leads to mostly useless results, since some builds include migrations etc and we want a more consistent trend graph of how long our tests are taking.

  • Steve Munday commented
    March 14, 2018 15:28

    +1 this.

    Half of our runs are on master, and half are on PR status checks.  The PR status checks are not shown in Insights because they are always on different branches.  Those are the ones more likely to fail, and therefore more interesting to analyze.