Filing a separate bug is too much an effort for users. Asking them to apply the Findit-Wrong label is more appropriate, and our team (at least you) should subscribe for bugs updates with that label and follow up.

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

commit 5ccfa5d98190b1a5b9fa937bec3d14dc5d367b7a
Author: Jeffrey Li <lijeffrey@chromium.org>
Date: Thu Jun 14 19:13:09 2018

[Findit] Flake Aanlyzer - Bug template for wrong results

Currently the bug template instructs sheriffs to assign wrong results back
to Findit team. However the bug is still valid for flakiness, even though
the culprit is wrong. The bug should instead be assigned to a developer to
fix the flakiness, and Findit's wrong result should be filed as a separate
bug.

This change clarifies the instructions for sheriffs and creates a bug
template specific to the analysis with the wrong result so a bug against
Findit can be filed in just 2 clicks.

Bug:  846506 
Change-Id: I239a420c6e4ddf51e32748693b446d43cd1a967b
Reviewed-on: https://chromium-review.googlesource.com/1089996
Commit-Queue: Jeffrey Li <lijeffrey@chromium.org>
Reviewed-by: Shuotao Gao <stgao@chromium.org>

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