[messaging app] should be able to send direct message to group member from menu
Bug #1458914 reported by
Bill Filler
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu UX |
Fix Released
|
High
|
Olga Kemmet | ||
messaging-app (Ubuntu) |
Fix Released
|
High
|
Tiago Salem Herrmann |
Bug Description
Steps to reproduce:
- receive a group message (MMS chat needs to be enabled)
- open the message
- on the header, click on the Contacts avatar
- a list of recipients is displayed with the recipients of the message
- click on one of the recipients in the list
Expected Results
- should open a new message to the selected recipient
Actual results:
- click on the recipient causes no action
--------------UX comment-----------
As per new design (please refer to the latest UX spec) the GROUP icon is replaced with a INFO icon where you can review the list with group members. Tapping on a list item from this view should allow user to start a new conversation with the selected contact.
Related branches
lp:~tiagosh/messaging-app/open-individual-chat
- Gustavo Pichorim Boiko (community): Approve
- PS Jenkins bot: Needs Fixing (continuous-integration)
-
Diff: 261 lines (+87/-15)5 files modifieddebian/control (+1/-0)
src/qml/Messages.qml (+20/-3)
tests/autopilot/messaging_app/emulators.py (+7/-3)
tests/autopilot/messaging_app/fixture_setup.py (+36/-0)
tests/autopilot/messaging_app/tests/test_messaging.py (+23/-9)
Changed in messaging-app (Ubuntu): | |
importance: | Undecided → High |
assignee: | nobody → Tiago Salem Herrmann (tiagosh) |
summary: |
- should be able to send direct message to group member from menu + [messaging app] should be able to send direct message to group member + from menu |
Changed in ubuntu-ux: | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Olga Kemmet (olga-kemmet) |
importance: | Medium → High |
description: | updated |
Changed in ubuntu-ux: | |
status: | Triaged → Fix Committed |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.