New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 702704 link

Starred by 5 users
Status: Untriaged
Owner: ----
Cc:
█ jparent@chromium.org
lafo...@chromium.org
jrobbins@chromium.org
estaab@chromium.org
█ bgoldman@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Task



Sign in to add a comment

Allow googlers to report issues without a wizard

Project Member Reported by no...@chromium.org, Mar 17 2017 
LUCI is a next-gen CI of Chromium and being used by non-Chromium teams, such as Fuchsia. Not all of Fuchsia team members have chromium accounts, but they need to be able to report bugs. Today "New issue" button takes them to a wizard that reports a Chrome bug, so they cannot create a bug for LUCI.

Solutions could be:
- allow *@google.com to file bugs without the wizard
- create a new monorail project for LUCI

Comment 1 by lafo...@chromium.org, Mar 17 2017

Cc: jrobbins@chromium.org
If it's a tool chain that will be used outside of Chromium, creating a separate project for LUCI might make the most sense.

Otherwise, there are plans to unify accounts and add all @google.com folks as project members in Q2, which should have the requested behavior as a side effect (i.e. project members don't see the wizards, and they'd be treated as normal project members w/ contributors +Google rights).

Comment 2 by no...@chromium.org, Mar 17 2017 

(LUCI is a replacement for Buildbot)

Comment 3 by jrobbins@chromium.org, Mar 17 2017 

Yeah,  issue monorail:172  will address this.

Until then, you could give them a go/ link that goes directly to /p/chromium/issues/entry, even with some template or fields specified in the URL.

Or, you could ask them to add their user group to g/chromium-bug-access so that they all become /p/chromium members.

Comment 4 Deleted

►

Sign in to add a comment