[User story] Disable notifications on lockscreen - As a user when I set lockscreen remotely from the Where's My Fox website, notifications on the lockscreen should be disabled

RESOLVED FIXED

Status

Firefox OS
FindMyDevice
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: vkrishnamoorthy, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)
Bug Flags:
in-moztrap +

Firefox Tracking Flags

(feature-b2g:2.0)

Details

(Whiteboard: [ucid:Services12, 2.0:p1, ft:services])

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
User Story:
As a user when I set lockscreen remotely from the Where's My Fox website, notifications on the lockscreen should be disabled

Rationale:
Notifications on the lockscreen can have personal information such as missed calls, sms and email notifications which can be read by anyone who finds the phone.

Updated

4 years ago
Whiteboard: [ucid:Services12, 1.4:p1, ft:services]

Updated

4 years ago
Whiteboard: [ucid:Services12, 1.4:p1, ft:services] → [ucid:Services12, 2.0:p1, ft:services]

Updated

4 years ago
feature-b2g: --- → 2.0
Summary: [WMF][Story]Disable notifications on lockscreen - As a user when I set lockscreen remotely from the Where's My Fox website, notifications on the lockscreen should be disabled → [User story] Disable notifications on lockscreen - As a user when I set lockscreen remotely from the Where's My Fox website, notifications on the lockscreen should be disabled

Updated

4 years ago
Flags: in-moztrap+
QA Contact: kglazko

Updated

4 years ago
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED

Comment 1

4 years ago
Created attachment 8446038 [details]
Notification messages display despite lost mode.

This probably needs to be examined further, this may be a regression.

Updated

4 years ago
blocking-b2g: --- → 2.0?
Technically this is a user story. What should be nomed here instead is the bug described in comment 1, so I'm clearing the nom & suggesting that a different bug be filed for comment 1.
blocking-b2g: 2.0? → ---
I think this is covered in bug 1030448.
You need to log in before you can comment on or make changes to this bug.