[Findit] Flake Analyzer - Make monorail bug optional when triggering new analysis manually |
|||
Issue descriptionMonorail bugs are currently mandatory for triggering flake analysis, but can be cumbersome and not necessarily accurate for tests that are fixed. Instead, this field should be made optional and marked as such in the UI
,
Nov 8 2017
,
Jan 4 2018
The following revision refers to this bug: https://chromium.googlesource.com/infra/infra/+/f915f273617cf5db17685573457e133556d3fb78 commit f915f273617cf5db17685573457e133556d3fb78 Author: Brandon Wylie <wylieb@chromium.org> Date: Thu Jan 04 21:28:24 2018 [Findit] Make bug id optional when triggering a flake analysis Right now a bug id is required if triggering from the UI. It isn't required on the backend, so remove it on the frontend and tell the user that. Bug:782457 Change-Id: I8b0a316fabf9424ffe800382070bb9cf47fbf858 Reviewed-on: https://chromium-review.googlesource.com/847953 Commit-Queue: Brandon Wylie <wylieb@chromium.org> Reviewed-by: Jeffrey Li <lijeffrey@chromium.org> Reviewed-by: Shuotao Gao <stgao@chromium.org> [modify] https://crrev.com/f915f273617cf5db17685573457e133556d3fb78/appengine/findit/templates/home.html
,
Jan 10 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by wylieb@chromium.org
, Nov 8 2017