Sometimes a validation will fail due to tests, which can take a long time in some cases (hours). I don't think I would expect the user to remain on that view for that amount of time, so I would want a way to review a validation at a later date. This would also go a long way in being able to review validations / deployments that were created by other users, which failed to complete. I actually think that the latter point is the bigger one for me as a team manager. If one of my devs fails to validate or deploy something, I want to be able to review or see that failure on my dashboard just like any of my attempts.

Just to expand on this, another reason to be able to view failed deployments is for troubleshooting purposes. It's not completely clear everything that is being deployed in the package, so being able to navigate to the actual deployment in the case of a failure, and dig into the package (i.e. download the zip), it would help push towards troubleshooting certain deployment issues.

Just to let you know, as a smaller extra piece of functionality to what's currently available - you can now export the details of deployment errors and failed tests to CSV files when there's a failure with package validation and/or a deployment failure. I know it's not exactly what you're after, but it may prove useful in some cases for you.

I feel like I've wanted this features as well. But I think this was back when I couldn't retry a deployment. I was left checking the boxes all over again.

Your draft feature actually is a good help to get around this, like you said.

Would expect the failed deployments/validations to be in the validated package history, maybe with a filter giving the ability to see only successful, failed or all, just like the scheduled tests history in "Test run details" (All tests, Failed tests, Passed tests).