FYI: if the blocking bug is in another project, so we need to prefix the project name like above.

Ah, my bad.

The following revision refers to this bug:
  https://chromium.googlesource.com/infra/infra/+/2d91b6863d243990d79bbf8effea620b004de2ba

commit 2d91b6863d243990d79bbf8effea620b004de2ba
Author: Brandon Wylie <wylieb@chromium.org>
Date: Tue Feb 06 02:55:00 2018

[Findit] Instrument bug filing to use CustomFields instead of labels

Labels can be added and removed freely and easily, which makes them
an inefficient method to track long-lived information, and arbitrary
labels are generally discouraged in monorail. Since Findit wants
the information about Flaky Tests to stick around even after the
bug has been resolved, custom fields are a better way to track
test information for bugs.

When this change deploys, I'll manually port over any existing bugs.

Bug:780110
Change-Id: I4504c8b74c25e350c403a9b449b065c97b77c2df
Reviewed-on: https://chromium-review.googlesource.com/898064
Commit-Queue: Brandon Wylie <wylieb@chromium.org>
Reviewed-by: Shuotao Gao <stgao@chromium.org>
Reviewed-by: Jeffrey Li <lijeffrey@chromium.org>

[modify] https://crrev.com/2d91b6863d243990d79bbf8effea620b004de2ba/appengine/findit/services/flake_failure/issue_tracking_service.py
[modify] https://crrev.com/2d91b6863d243990d79bbf8effea620b004de2ba/appengine/findit/pipelines/flake_failure/test/create_bug_for_flake_pipeline_test.py
[modify] https://crrev.com/2d91b6863d243990d79bbf8effea620b004de2ba/appengine/findit/pipelines/flake_failure/create_bug_for_flake_pipeline.py
[modify] https://crrev.com/2d91b6863d243990d79bbf8effea620b004de2ba/appengine/findit/services/flake_failure/test/issue_tracking_service_test.py