Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Use Markdown for this comment
Set severity, which reflects how much the issue affects the use of the product
Change issue status back to 'Assigned'
Pending code changes (auto-populated)
Googlesource release version that first features the resolution of this issue. [ID: 1154560]
The TargetMilestone field is used to define when the engineer the bug is assigned to expects to fix it. [ID: 1154531]
Select items in the list
The version field defines the version of the software the bug was found in. [ID: 1154637]
Set the version(s) of the product affected by this issue (comma-separated list)
Set the version(s) of the product in which the issue should be fixed (comma-separated list)
Set the version(s) of the product in which the issue fix was verified (comma-separated list)
Set if this issue occurs in production
Set Reporter
Set Type
Set priority, which reflects how soon the issue should be fixed
Set Status
Set Assignee
Set Verifier
View or edit staffing
View issue level access limits(Press Alt + Right arrow for more information)
Description
1. notice spam on a CL.
2. open CL, see comment where they spam
Expected: There's a link/button to report user.
Actual: No abuse reporting built into gerrit.
3. magically know go/fix-chrome-git template link
4. get user's email address: A bit tedious
4.1 Expand most recent spam comments
4.2 Hover to get email address?
4.3 Can't select and copy that email address
4.4 Right click to Inspect with Chrome developer tools
4.5 Find email in adjacent HTML