There are many cases which it unclear whether a bisect is already kicked off for a performance regression bug. This makes it:
1) Hard for people to know whether they should making new bisect for the existing bug, unless they make 3,4 clicks later into the dashboard & verified existing trybot jobs.
2) Hard for performance bug triager to know whether the associated should be looked at even if someone just kicked off a new bisect for that bug few days earlier.

We should consider making perf dashboard post notification to crbug when a bisect is kicked off.