947161 - [DSDS][Message] Message Report shows received SIM information

Status: VERIFIED FIXED

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

Description

[Wilfred Mathanaraj [:WDM]]

As a user I want to know which SIM, phone number the message was received on in the message report

Acceptance Criteria

AC1: For SIM options I want to see SIM1 or SIM2
AC2: For phone number I want to see the phone number and if this can not be obtained I want to see "unknown"

Comment 1

[Julien Wajsberg [:julienw]]

This will probably be done in bug 947142.

Comment 2

[Joe Cheng [:jcheng] (please needinfo)]

features should not block release, remove blocking flag

Comment 3

[Steve Chung [:steveck]]

Although I landed the SIM information patch in bug 947142 and this one could be closed, I still want to clarify some UX behavior missed in bug 947142 before closing this one. Hi Ayman, Wilfred said we should display 'unknown' when the phone number is unavailable. The sad news is we could not guarentee phone number could be accessible on every SIM card(we fail to access phone number quite often actually). Do you think we should display 'unknown' for the unavailable SIM information, or just discard the field(SIM 1 , carrier, unknown - > SIM 1 , carrier)?

Comment 4

[ayman maat :maat]

(In reply to Steve Chung [:steveck] from comment #3)
> Although I landed the SIM information patch in bug 947142 and this one could
> be closed, I still want to clarify some UX behavior missed in bug 947142
> before closing this one. Hi Ayman, Wilfred said we should display 'unknown'
> when the phone number is unavailable. The sad news is we could not guarentee
> phone number could be accessible on every SIM card(we fail to access phone
> number quite often actually). Do you think we should display 'unknown' for
> the unavailable SIM information, or just discard the field(SIM 1 , carrier,
> unknown - > SIM 1 , carrier)?

Hey Steve. you can just discard it. The rational behind this is that if the phone number is unavailable as far as i am aware it will always be unavailable ...which means that outputting 'unknown' just creates noise on the interface.

Comment 5

[Paul Yang [:pyang] (away)]

in-moztrap+
https://moztrap.mozilla.org/manage/cases/?pagenumber=1&pagesize=20&sortfield=created_on&sortdirection=desc&filter-tag=2578&filter-productversion=164

Comment 6

[Steve Chung [:steveck]]

(In reply to ayman maat :maat from comment #4)
> (In reply to Steve Chung [:steveck] from comment #3)
> > Although I landed the SIM information patch in bug 947142 and this one could
> > be closed, I still want to clarify some UX behavior missed in bug 947142
> > before closing this one. Hi Ayman, Wilfred said we should display 'unknown'
> > when the phone number is unavailable. The sad news is we could not guarentee
> > phone number could be accessible on every SIM card(we fail to access phone
> > number quite often actually). Do you think we should display 'unknown' for
> > the unavailable SIM information, or just discard the field(SIM 1 , carrier,
> > unknown - > SIM 1 , carrier)?
> 
> Hey Steve. you can just discard it. The rational behind this is that if the
> phone number is unavailable as far as i am aware it will always be
> unavailable ...which means that outputting 'unknown' just creates noise on
> the interface.

Thanks! I think we can close this one for now.

Comment 7

[Paul Yang [:pyang] (away)]

Verified by existing test cases