Closed Bug 1119992 Opened 5 years ago Closed 4 years ago

direct calls should tell user "contact unavailable", not "something went wrong" when callee doesn't pick up

Categories

(Hello (Loop) :: Client, defect, P4)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX
Blocking Flags:
backlog backlog+

People

(Reporter: dmose, Unassigned)

References

()

Details

(Whiteboard: [errors])

User Story

- Update code added by bug 1118061 to include the new timeout reasons from bug 1120375 (once decided)
+++ This bug was initially created as a clone of Bug #1118061 +++

Given this amount of user training, I'm concerned that a substantial number of users may interpret every non-answer or busy as "the system is broken right now", which would effectively make the product seem extremely broken to those people, even when it's not.

Right now, reason=timeout in the client code covers several things:

* call not answered
* the other user is not logged in

and 

* call failed during setup

We need to display the "contact unavailable" message for the first two cases, but not the last one.
Whiteboard: [strings]
Depends on: 1120001
Depends on: 1120003
If we can, I'd like us to get this into 37, as it'll be a significant improvement in the messaging to users.

Taking initially to get this specified out.
Assignee: nobody → standard8
backlog: --- → Fx37?
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: [investigation initially]
Blocks: 1120001, 1120003
No longer depends on: 1120001, 1120003
Depends on: 1120375
Assignee: standard8 → nobody
User Story: (updated)
Assignee: nobody → jaws
Blocks: 1124365
See Also: → 1124381
Assignee: jaws → nobody
moving to 38 where work is being done.  uplift considered after patch is fixed and applied for through normal channels.
backlog: Fx37? → Fx38?
need to discuss with Dan/Jaws.  we are seeing a much higher volume of rooms growing and calls decreasing - so the error are a lower priority - though still there.  how much more effort are these bugs if we are considering rolling direct calling into rooms or changing UI?  the communication accuracy still valid - but lower priority as UX may change.
Priority: P2 → P4
Whiteboard: [investigation initially]
[Tracking Requested - why for this release]:

I'm concerned that a substantial number of users may interpret every non-answer or busy as "the system is broken right now", which would effectively make the product seem extremely broken to those people, even when it's not.

37 already has the necessary string changes to take this patch.
Never mind; was thinking of bug 1124381.
(In reply to sescalante from comment #3)
> need to discuss with Dan/Jaws.  we are seeing a much higher volume of rooms
> growing and calls decreasing - so the error are a lower priority - though
> still there.  how much more effort are these bugs if we are considering
> rolling direct calling into rooms or changing UI?  the communication
> accuracy still valid - but lower priority as UX may change.

It would depend on exactly what sort of changes we wanted to make.
backlog: Fx38? → backlog+
Rank: 45
Flags: firefox-backlog+
Whiteboard: [errors]
See Also: 1109866
We are currently reworking the Loop "user journey" (bug 1209713) and as part of this direct calls and contacts are being removed. Therefore closing direct call related bugs as wontfix.

Tracking id: directcallclosing
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.