New issue
Advanced search Search tips

Issue 762051 link

Starred by 4 users
Status: Available
Owner: ----
Cc:
tommycli@chromium.org
thestig@chromium.org
dpa...@chromium.org
rmis...@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Blocked on:
issue 696706

Previous locations:
gerrit:6947


Sign in to add a comment

Bug number should be validated against bug tracker

Project Member Reported by tommycli@chromium.org, Aug 4 2017 
This has happened to me:

1. User fat fingers or mis-pastes a bug number.
2. CL is committed, and now the wrong bug number cannot be fixed.

My recommendation:

3. When user uploads or clicks "Submit to CQ" for Chromium, check that the linked bug number is actually an Open bug that the user also owns.

If the bug is closed or another user owns it, show a modal confirmation dialog saying: "Hey it looks like you're submitting to Bug "This title", are you sure?"

Comment 1 by logan@google.com, Sep 5 2017

Labels: -Priority-3 Proj-Gerrit-Migration
This isn't on the Gerrit roadmap, but maybe chrome-infra would like to implement this feature in their customizations?

Comment 2 by logan@google.com, Sep 5 2017

Project: chromium
Moved issue gerrit:6947 to now be issue chromium:762051.

Comment 3 by aga...@chromium.org, Sep 11 2017

Blockedon: 696706
Components: Infra>Codereview>Gerrit
Labels: Milestone-Afterglow
Status: Available (was: New)
Yep, this would be a great feature for the Gerrit Bugdroid plugin to grow.

Comment 4 by tommycli@chromium.org, Sep 11 2017 

agable: Awesome! It would make my life way better!

Comment 5 by aga...@chromium.org, Jan 3 2018

Labels: -Milestone-Afterglow
Removing Milestone-Afterglow, as it has ceased to have meaning. More refined milestones may be added back in the near future.

Comment 6 by aga...@chromium.org, Mar 27 2018

Labels: Pri-3
►

Sign in to add a comment