I actually don't think surfacing the link to the raw data in the buildbot logs will go far enough. What we really need is for the raw data to be linked to either from the bug or from the job status page (https://chromeperf.appspot.com/buildbucket_job_status/8986805323774654704). Buildbot logs are basically unreadable because almost all of the links are broken, and it's totally unclear which links to click. I can figure out how to read the buildbot logs, but I'm not going to be able to teach my entire rotation of SWEs how to do it.

We are working on a new version of bisect which will run the bisection logic from an app engine service, and show a web ui for the results:
https://docs.google.com/document/d/1FKPRNU2kbPJ15p6XHO0itCjYtfvCpGt2IHblriTX1tg/edit#

The reason is that clear UX like this is really hard to shoehorn in from buildbot. I think we should focus on making this better in pinpoint above trying to figure out how to fix the buildbot UX

Totally agree. Sidestepping buildbot UX is the right solution here. That's why it would be great to add a link to the data in the chromeperf job status page.