Closed Bug 876632 Opened 11 years ago Closed 10 years ago

[User Story] Service numbers (SDN) not imported from the SIM

Categories

(Firefox OS Graveyard :: Gaia::Contacts, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(feature-b2g:2.0, tracking-b2g:backlog, b2g-v2.0 fixed)

VERIFIED FIXED
2.0 S3 (6june)
feature-b2g 2.0
tracking-b2g backlog
Tracking Status
b2g-v2.0 --- fixed

People

(Reporter: juanpbf, Assigned: mai)

References

Details

(Keywords: feature, Whiteboard: [priority])

User Story

AC1: When user clicks on import contacts from SIM card, both ADN and SDN contacts will be imported.

AC2: There won't be any distinction between ADN and SDN contacts, all of them will be shown in one list without any type of visual indicator. SDN contacts will be part of the Contact List with no structural distinction between them and other contacts.

Attachments

(1 file)

46 bytes, text/x-github-pull-request
jmcf
: review+
Details | Review
When importing SIM contacts, the Service Dialing Numbers (SDN) are not imported and they should.

Reproducible in Ikura with any build

shall we nominate it for leo? --> what do you think David?
Flags: needinfo?(dpv)
Hi!

I think this is not a blocking issue for 1.0.1. Preloaded contacts are preloaded in the commercial devices, so it should be not very important. 

Thanks!
David
Flags: needinfo?(dpv)
I think this could be included for leo. Nominating it.
blocking-b2g: --- → leo?
Could be included makes this sound like additional feature work and too late for v1.1 - if this is not championed by a partner and assigned a milestone it will have to wait for a future release.
blocking-b2g: leo? → -
This issue has come back to light during the official IOT for Open C -- The operator has reported it again. 

What's current status? Is this going to be included in 1.3? if not, can we nominated it at least for 1.4?
I have a quick question, when we are suppose to import SDN contacts?

As an option form the import menu, we import them when user clicks on import contacts from sim (importing both ADN and SDN)?

Flagging Mr Wildfred for some input
Flags: needinfo?(wmathanaraj)
this is what would make sense if we need to import SDN. When we import contacts from SIM it should then import ADN, SDN all normal contacts.
Flags: needinfo?(wmathanaraj)
Assignee: nobody → fernando.campo
blocking-b2g: - → 1.4?
OS: Windows 7 → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Could be landed until March 17th if ready, not a release blocker
blocking-b2g: 1.4? → ---
I've been testing this, but due both to lack of information (no documentation on the function we need to call from mozContacts or icc, neither on wiki or mdn) and not having a SIM with sdn contacts inside, I'm gonna keep it aside till next week, when I'll try to get my hands on it.
We would need input about how SDN contacts should be managed (specific list?, part of the contact list?), asking UX for their PoV (spec). Thanks!
Flags: needinfo?(aymanmaat)
(In reply to Noemí Freire (:noemi) from comment #9)
> We would need input about how SDN contacts should be managed (specific
> list?, part of the contact list?), asking UX for their PoV (spec). Thanks!

Well, the design intention behind this has always been that *all* contacts could be imported from SIM. On my test SIMs the SDNs are part of the Contact List with no structural distinction between them and other contacts which is why there was never any specific reference to SDNs in the specification.

If there are instances were SDNs exist as a separate list to the Contact List on a SIM and therefore should exist as a separate list on the device please advise me of how this is expected to work (presentation of SDN on SIM, during import and when the SDN are on the phone itself) and I will define and produce a specification accordingly. Screenshots or video would be good. Please ni? me if any are forthcoming
Flags: needinfo?(aymanmaat)
the SDN list shouled be managed as part of the contact list
but now the question is the sim card has SDN  but did not display in the contact list
blocking-b2g: --- → 1.5?
blocking-b2g: 1.5? → 1.3?
Not a regression, so this is should not block 1.3.
blocking-b2g: 1.3? → backlog
can this problem be solved recently?
Flags: needinfo?(cawang)
Hi Carrie,

Could you please provide UX interaction flow here?. Thanks!
I think for this bug, we shall let users import both SDN and ADN with other contacts for now. We shall display these numbers with normal contacts and let users filter their preferred/ important contacts from this long list in the future (could be added into future plan). Thanks!
Flags: needinfo?(cawang)
Whiteboard: [priority]
Keywords: feature
feature-b2g: --- → 2.0
Assignee: fernando.campo → mri
feature of 2.0 needs to be landed before FL (Sprint3)
Target Milestone: --- → 2.0 S3 (6june)
Attached file patch v1.0
Attachment #8431446 - Flags: review?(jmcf)
Comment on attachment 8431446 [details] [review]
patch v1.0

as we have talked offline we need to refine a bit more the solution, so let's cancel the review for the moment.
Attachment #8431446 - Flags: review?(jmcf)
QA Contact: lolimartinezcr
Attachment #8431446 - Flags: review?(jmcf)
Comment on attachment 8431446 [details] [review]
patch v1.0

The only thing I'm missing is a test that checks whether the importer.onerror is called when the request for ADN Contacts is on error. Please add it and land when Travis is green
Attachment #8431446 - Flags: review?(jmcf) → review+
Master: 6a083e741bdf945bbdff32edb78ce7476199128a
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Tested and working
Hamachi
2.0
Platform versión 32.0a1
Build ID: 20140606084902
Git commit: 902b0cdf
Status: RESOLVED → VERIFIED
Updating the title as this bug is a User Story and including also the ACs agreed with UX during the implementation. 

QA already verified this US based on them during last week so the corresponding bugs should be exported in Moztrap.
User Story: (updated)
Summary: Service numbers (SDN) not imported from the SIM → [User Story] Service numbers (SDN) not imported from the SIM
attachment 8431446 [details] [review] pacth is united, but doesn't work, could you tell me the verified,need to support
We had tested master-Flame, today build, and the import of ADN and SDN numbers is working fine. If you had any issue here, please open a new bug and provide more info about your testing environment.
I will open a new bug for you,We think FireFox can support SDN UI , SDN can be found under Settings->Call Settings->Operator Service
(at the bottom of the menu).
blocking-b2g: backlog → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: