Simon, can you triage?

Workaround is a bit painful:
1. Manually file crbug with appropriate fields populated.
2. Then associate it as "Existing Bug" in the alert dashboard.
3. Then start a bisect.
The last two steps can be done in any order.

I've manually filed bugs to track bisection of 7 different groups of alerts today. Please fix soon :)

This is strange, don't think any code has changed in that area, will take a look!

Can't find anything wrong on our end, or any changes to this code recently so I've filed https://bugs.chromium.org/p/monorail/issues/detail?id=4042 for the monorail team

 Issue 865164  has been merged into this issue.

Fix incoming, also upped this to p0 since it blocks sheriffing completely.

The following revision refers to this bug:
  https://chromium.googlesource.com/catapult/+/26a1ccee228add57dfa2b85a2568e49d497e63b0

commit 26a1ccee228add57dfa2b85a2568e49d497e63b0
Author: Simon <simonhatch@chromium.org>
Date: Thu Jul 19 18:57:14 2018

Dashboard - Add required field to body when creating bugs.

This was caused by a change on the monorail side, when they switched
endpoints libraries enforces that this field is set.

TBR=eakuefner@chromium.org
Bug:  chromium:865147 
Change-Id: I6e3b1baff51e9bb950efc4aa30efe3aa18fd4f0c
Reviewed-on: https://chromium-review.googlesource.com/1143681
Commit-Queue: Simon Hatch <simonhatch@chromium.org>
Reviewed-by: Simon Hatch <simonhatch@chromium.org>

[modify] https://crrev.com/26a1ccee228add57dfa2b85a2568e49d497e63b0/dashboard/dashboard/services/issue_tracker_service_test.py
[modify] https://crrev.com/26a1ccee228add57dfa2b85a2568e49d497e63b0/dashboard/dashboard/services/issue_tracker_service.py

Should be fixed, deployed a dev version before that which file bugs successfully.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7e498d8b1d30cb9e3fa7e7065f567ebafae5d1a7

commit 7e498d8b1d30cb9e3fa7e7065f567ebafae5d1a7
Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Thu Jul 19 21:09:45 2018

Roll src/third_party/catapult 2ec2b508e610..26a1ccee228a (4 commits)

https://chromium.googlesource.com/catapult.git/+log/2ec2b508e610..26a1ccee228a


git log 2ec2b508e610..26a1ccee228a --date=short --no-merges --format='%ad %ae %s'
2018-07-19 simonhatch@chromium.org Dashboard - Add required field to body when creating bugs.
2018-07-19 dtu@chromium.org [pinpoint] Clean up deprecated isolate code.
2018-07-19 wangge@google.com Added script to generate milestone version release date table
2018-07-19 nednguyen@google.com Memorize the ts_proxy_server's traffic settings and only set them when they


Created with:
  gclient setdep -r src/third_party/catapult@26a1ccee228a

The AutoRoll server is located here: https://catapult-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel

BUG= chromium:865147 , chromium:828778 , chromium:863390 ,chromium:861534
TBR=sullivan@chromium.org

Change-Id: I75a636b6d6ce1cabb7b356876f22808022a4eca0
Reviewed-on: https://chromium-review.googlesource.com/1143986
Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#576625}
[modify] https://crrev.com/7e498d8b1d30cb9e3fa7e7065f567ebafae5d1a7/DEPS