Rollback system is confusing

Often, we know that e.g. "SHA 599db8 is good" or "SHA 32df81 is bad"

So I see this, and I think, clicking this button, what will happen? Will I be on 892... or 599... after the operation completes? Then I look to the deploy below, see the same SHA referenced, and have to think some more. In the confusion of an incident, this potential for confusion doesn't help my confidence in picking the right course of action swiftly. Maybe I just don't rollback enough, but I figure that I cannot be the only one.

Main proposal

Given knowledge that "SHA 599db8 is good" or "SHA 32df81 is bad", I think that perhaps it would be more clear if the rollback button said directly instead, Rollback to 599db80428, because to this deploy seems rather obvious and doesn't add much

Secondary proposal

Further, putting the full SHA from git log onto the message somewhere onto the page could help with cmd+f => paste in ba253674eb4831031fbf6131ec19874d80aba975, but I can accept grabbing 8 or so chars from git log and truncating it myself

Thoughts?

Start by locating the rollback button and the deploy details shown in the deployment coordination UI, then compare which commit SHA each currently represents. Done means the rollback action clearly names its target SHA, with the full SHA available on the page for searching; no specific file or test is named in the issue.