Closed Bug 911878 Opened 12 years ago Closed 11 years ago

[zffos1.1][P2][Contract]When you have more than one contact in DUT native addressbook with the same MSISDN, both Call History and Messages Thread reports this fact, but in a different way.

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: fang.chen1, Unassigned)

Details

Built ID 20130823171628 Device: Ikura QC RIL version: "ro.build.firmware_revision=V1.01.00.01.019.180" gaia commit: 4916f82 Merge branch 'zte/ics_strawberry_cdr' of ssh://10.67.16.41:29418/quic/lf/releases/gaia into ics_strawberry_cdr gecko commit: a1c2bb0 ZRL modify ACCEPT Http head for MMS A.- Overview Description (technical background, concise explanation of the bug): When you have more than one contact in DUT native addressbook with the same MSISDN, both Call History and Messages Thread reports this fact, but in a different way. ________________________________________________________________________________ B.- Steps to Reproduce (initial conditions, required resources, step by step instructions to reproduce): 1. Turn the DuT on with a SIM card. 2. Add two contacts in DUT native addressbook with same MSISDN, one of them is called Mobil1 and the other Mobil2 3.- Go to Contactos, select the Mobil1 contact and call it. 4.- Check the behavior. ________________________________________________________________________________ C.- Actual Result (current bad behaviour that is reported as a bug): When two contacts are saved with the same MSISDN, i.e Mobil1 and Mobil2, at call to the Mobil1, the DuT displays the label of the Mobil2. ________________________________________________________________________________ D.- Expected Result (correct behaviour wished): The labels should be displayed correctly. ________________________________________________________________________________
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.