Closed
Bug 1086219
Opened 10 years ago
Closed 10 years ago
[Loop] In "Shared links" tab, user doesn't see the phone number where a SMS was sent when contact has two or more phones numbers
Categories
(Firefox OS Graveyard :: Gaia::Loop, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: lolimartinezcr, Unassigned)
References
Details
(Whiteboard: [Test-Run1] [mobile app])
fireE (firee-kk-v2.0-SW2E3-1)
Loop version: 1.1 , 2168965
Prerequisites:
Device A logged in Loop application.
Device A with a contact saved with name and two valid phone number (no-Loop client)
STR:
1. Device A, taps in "contact" button.
2. Tap in contact with two contacts.
3. Call is dialing in Device A, after seconds "Share link" screen is showed.
4. Taps in "Message" button, select a phone number and taps in "Send message" button.
5. Taps in "X" button (close message application)
Actual result:
Devica A in "Shared links" tab, user doesn't see the phone number where a SMS was sent. Only see: name of contact, URL and time.
Expecte result:
User also should see the phone number where a SMS was sent.
Reporter | ||
Updated•10 years ago
|
Summary: [Loop][Loop] In "Shared links" tab, user doesn't see the phone number where a SMS was sent when contact has two or more phones numbers → [Loop] In "Shared links" tab, user doesn't see the phone number where a SMS was sent when contact has two or more phones numbers
Comment 1•10 years ago
|
||
According to the ACs in US bug 1034605 in the shared URL entry should be shown:
- Friendly name of the contact the URL was shared with (if available)
- ID of the contact the URL was shared with
I am not sure but I think that, due to the reduced space, the ID of the contact didn't fit in the "Shared URL" entry so with the contact name (in case it was available) was enough.
Anyway, be aware that in the ACs we are talking about showing the Contact name or the ID that we have tried to reach, not the specific phone number we have sent the SMS to. In fact, I can change or included more numbers before sending the SMS.
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•