Closed Bug 891249 Opened 6 years ago Closed 6 years ago

[User Story][WAP Push] MSISDN filtering

Categories

(Firefox OS Graveyard :: RIL, defect, P1)

x86
macOS
defect

Tracking

(blocking-b2g:koi+, firefox26 fixed)

VERIFIED FIXED
blocking-b2g koi+
Tracking Status
firefox26 --- fixed

People

(Reporter: bhuang, Assigned: bhuang)

References

()

Details

(Whiteboard: [ucid:WAP-Push3, FT:RIL, KOI:P1])

User story:

As an operator I want to define which MSISDNs can send wap push messages to user so the user is not spammed by adverts
Blocks: b2g-wap-push
Assignee: nobody → chulee
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 887156
This is a user story bug and it could contain gaia and gecko work. Re-open it to make sure gaia work is taken into consideration.
Assignee: chulee → bhuang
Status: RESOLVED → REOPENED
Depends on: 887156
Resolution: DUPLICATE → ---
What are the acceptance criteria for this user story?
blocking-b2g: --- → koi+
Flags: in-moztrap?(echu)
QA Contact: echu
Priority: -- → P1
Whiteboard: [ucid:WAP-Push3] → [ucid:WAP-Push3], [FT:RIL]
update acceptance criteria from backlog

Configure a MSISDN that can send WAP Push messages to the device. If the MSISDN sends a message to the device, it should be received properly. If another MSISDN sends a message, the device should not receive it (or at least user should not be notified)
Update test case URL.
Flags: in-moztrap?(echu) → in-moztrap+
Whiteboard: [ucid:WAP-Push3], [FT:RIL] → [ucid:WAP-Push3, FT:RIL, KOI:P1]
Summary: [WAP Push][User Story] MSISDN filtering → [User Story][WAP Push] MSISDN filtering
We can finish this one in this week.
Component: General → RIL
QA can verify.
Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → FIXED
Verify on following buid
Gaia: e58cfdac65fe644dc79fb3613fdaa9d9573537ac1378985810
Build: 20130912134644
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.