Easily see failed tests correlated to CI job parameters.

Pain point: To release your product or to merge a PR, you require run a battery of tests that exercise your products support matrix. In practice, this is done by running multiple Jenkins jobs with varying parameters. The problem occurs when tests fail. What operating system did they fail on? What browser version? What is the common thread? Answering this question is hard in products like Jenkins. Instead, you need a view of the failed tests that is associated to the test parameters.

Who is this for? Products with a support matrix. Usually an enterprise product.