When triaging Microbenchmarks and sys-perf, it's difficult to get any historical info about historical ups and downs in the trend graphs. There may exist a Jira ticket, but when just looking at the trend graph, there's no marker or link to say that this jump 3 weeks ago is a known issue. A lot of time is then wasted by the build baron re-discovering things that are already known.
We'd like to change the display so that, in addition to displaying change points, Build Failures are also rendered onto the trend graphs.
BF tickets have 'Evergreen Project', 'Failing Buildvariants', 'Failing Tasks' and 'First Failing Revision' / 'Fix Revision' fields that can be used to link to the point in the trend graphs.
When a BF and a Change Point exist for the same revision, the BF should take precedence (as this indicates that the change is known or is being worked on).