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

Issue 732832 link

Starred by 2 users

Issue metadata

Status: Closed
Owner:
Closed: Nov 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: ----
Type: Feature
Launch-Accessibility: NeedInfo
Launch-Exp-Leadership: NA
Launch-Leadership: NotReviewed
Launch-Legal: NotReviewed
Launch-Privacy: NotReviewed
Launch-Security: NotReviewed
Launch-Test: NotReviewed
Launch-UI: NotReviewed

Blocked on:
issue 737215



Sign in to add a comment

Notifications on Lock Screen

Project Member Reported by zalcorn@chromium.org, Jun 13 2017

Issue description

Feature description: Show notifications on the lockscreen for at-a-glance access, in a way that is privacy sensitive and low impact to standby battery.

Eng owner: tbd
Product owner: zalcorn

You should also have a Finch ambassador. Go to
https://g3doc.corp.google.com/analysis/uma/g3doc/finch/guide.md?cl=head
#finch-ambassador to get a Finch ambassador and CC them on this bug.

#################################################################
# Fill these surveys out as you are ready for various reviews.  #
#################################################################

Accessibility survey: The accessibility survey is included in a review bug
that will be filed by lpalmaro@. Please answer all questions there.

Legal survey: Email ctanaka@ (for non-Chrome OS) or jlchen@ (for Chrome OS)
to request a legal review.

Privacy survey: When you flip Launch-Status to Review-Requested, the
privacy team will be notified. Once they've triaged your
launch, a blocking privacy review bug will be filed. Fill out the privacy
survey included in that bug. Email yitingc@ for any questions.

Test survey (https://goto.google.com/chrome-test-questions):

UI survey: Email chrome-ui-review@ (for non-Chrome OS) or chromeos-ui-
review@ (for Chrome OS) to request a UI review if your launch will change
any user-visible strings, assets, animations, or workflows.

 

Comment 1 by r...@chromium.org, Jun 13 2017

Labels: -TL-tbd TL-rkc
Blockedon: 737215
Labels: -M-64
Removing a milestone until it is clear we want to do this.
Project Member

Comment 4 by sheriffbot@chromium.org, Feb 12 2018

This launch bug has not been modified in the last 90 days and has no milestone label. Please take a look and add appropriate milestone label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 5 by sheriffbot@chromium.org, May 14 2018

This launch bug has not been modified in the last 90 days and has no milestone label. Please take a look and add appropriate milestone label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by amin...@google.com, May 15 2018

Labels: Launch-Exp-Leadership-NA
We've added two new bits to the Launch template - Launch-Exp-Leadership and Launch-Leadership - to capture leadership approval for new features.  The Launch-Exp-Leadership bit is meant to capture approval for Finch-based experimentation in the stable channel.  However, since Chrome OS tends not to use Finch to experiment in the stable channel, setting this bit to NA for all Chrome OS-only launches.

Ping amineer@ with any questions / concerns.

Comment 7 by amin...@google.com, May 16 2018

Labels: Launch-Leadership-NotReviewed
Per updates to go/newChromeFeature, setting new Launch-Leadership bit (meant to capture leadership approval) to NotReviewed.  Ping amineer@ for questions.
Labels: -Launch-Accessibility-NotReviewed a11y-filed Launch-Accessibility-NeedInfo
Labels: Type-Feature
[Bulk edit]: converting my launch bugs without target milestones to Feature Requests for better organizational sanity. They will retain Restrict-View-Google. Please ping me with any issues.
Status: Closed (was: Assigned)
Believe this is being worked on elsewhere.

Sign in to add a comment