Suggestion for sippy component readiness. I am debugging why our boxes are light-green and it would help me a lot if "Test Details Report" was able to distinguish two cases:

• new (4.15) job exists, but does not contain the test, like periodic-ci-openshift-release-master-ci-X.X-e2e-aws-ovn here misses test "read-write-once-pod should block a second pod from using an in-use ReadWriteOncePod volume" in 4.15 (the test has been renamed upstream and I need to update test matching)
• new (4.15) job does not exist at all, like periodic-ci-openshift-release-master-ci-X.X-e2e-aws-crun-wasm on the same page - 4.14. job exists, 4.15 does not

UX idea: a new field "Job runs: XYZ" in "Sample Info" would tell me that a job has nozero runs, but test has 0 successes and 0 failures, i.e. a test is missing. And the "Job runs" could be clickable and lead to the full job history, regardless if it contained the test or not...