Closed Bug 888919 Opened 7 years ago Closed 6 years ago

[User Story] Handling active FDN status

Categories

(Firefox OS Graveyard :: Gaia::Dialer, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:koi+)

RESOLVED FIXED
blocking-b2g koi+

People

(Reporter: wmathanaraj, Assigned: kaze)

References

Details

(Keywords: feature, Whiteboard: [MOZ][UCID:Comms8, FT:comms, KOI:P1], [u=commsapps-user c=dialer p=0][Sprint 2][Status: UX provided initial spec, Gaia working on it])

Attachments

(1 file)

User Story:

As a user, if I dial any number in the dialer or by selecting a contact in the contacts app, outside what is allowed as per the FDN list, I expect to be informed that FDN mode is active and call is not placed.

As a user I expect the same restrictions to apply for SMS and MMS.

As a user I expect to be able to dial any emergency number even if FDN mode is active.

Precondition:

* SIM supports FDN
* FDN mode is active


Acceptance Criteria:

* Message is displayed to user if call can not be placed due to FDN restriction
* Message is displayed to user if SMS or MMS can not be sent due to FDN restrictions
* Any error messages are displayed to user
Depends on: 889251
The gecko end has supported the FDN functionality as well as the corresponding API. The UI implementation on the Gaia end is at bug 849015.
Depends on: 849015
(In reply to Gene Lian [:gene] from comment #1)
> The gecko end has supported the FDN functionality as well as the
> corresponding API. The UI implementation on the Gaia end is at bug 849015.

Sorry, I mean bug 840915.
Depends on: 840915
No longer depends on: 849015
OS: Mac OS X → Gonk (Firefox OS)
Hardware: x86 → ARM
Component: Gaia::Settings → Gaia::Dialer
Whiteboard: [ucid:Comms8] → [ucid:Comms8], [u=commsapps-user c=dialer p=0]
listed as must have in v1.2 for COMM team. koi+
blocking-b2g: koi? → koi+
Flags: in-moztrap?
Comms6, Comms7, Comms8
MozTrap #9026, #9027, #9028, #9035, #9036, #9038, #9039, #9040, #9041
Flags: in-moztrap? → in-moztrap+
Whiteboard: [ucid:Comms8], [u=commsapps-user c=dialer p=0] → [ucid:Comms8 KOI:P1], [u=commsapps-user c=dialer p=0]
Assignee: nobody → jcheng
Whiteboard: [ucid:Comms8 KOI:P1], [u=commsapps-user c=dialer p=0] → [UCID:Comms8, FT:comms, KOI:P1], [u=commsapps-user c=dialer p=0]
Assignee: jcheng → nobody
Whiteboard: [UCID:Comms8, FT:comms, KOI:P1], [u=commsapps-user c=dialer p=0] → [MOZ][UCID:Comms8, FT:comms, KOI:P1], [u=commsapps-user c=dialer p=0]
Whiteboard: [MOZ][UCID:Comms8, FT:comms, KOI:P1], [u=commsapps-user c=dialer p=0] → [MOZ][UCID:Comms8, FT:comms, KOI:P1], [u=commsapps-user c=dialer p=0][Sprint 1][Status: UX workong on this towards end of Sprint 1]
Whiteboard: [MOZ][UCID:Comms8, FT:comms, KOI:P1], [u=commsapps-user c=dialer p=0][Sprint 1][Status: UX workong on this towards end of Sprint 1] → [MOZ][UCID:Comms8, FT:comms, KOI:P1], [u=commsapps-user c=dialer p=0][Sprint 2][Status: UX provided initial spec, Gaia working on it]
I have provided Kaze with two options for this solution. I am waiting on Kaze to give technical feedback before defining which solution is final and closing the wireframes. 

so needinfo to Kaze to provide feedback so wireframes can be closed
Flags: needinfo?(kaze)
I’ve already implemented the first option (very simple, patch to come) but I like the second option a lot.

I’ll send a patch this week with the first option and I’ll open another bug to propose a patch for the second option.
Assignee: nobody → kaze
Flags: needinfo?(kaze)
(In reply to Fabien Cazenave [:kaze] from comment #6)
> I’ve already implemented the first option (very simple, patch to come) but I
> like the second option a lot.
> 
> I’ll send a patch this week with the first option and I’ll open another bug
> to propose a patch for the second option.

ok kaze, thanks for letting me know
Flows have been with Kaye since Paris, so no new work here. Just formally publishing the document to close it off

Wireframe release note

new wireframes
- none

updated wireframes
- none

deleted wireframes
- none

new flows
- FDN : Handling FDN status (implementation for v1.2)
- FDN : Handling FDN status (implementation for v1.3)

updated flows
- none

deleted flows
- none
Blocks: 913421
No longer blocks: 913421
Depends on: 913421
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.