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

Status: RESOLVED WONTFIX

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

Description

[Dan Mosedale (:dmosedale, :dmose)]

+++ 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.

Comment 1

[Mark Banner (:standard8)]

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.

Comment 2

[:shell escalante]

moving to 38 where work is being done.  uplift considered after patch is fixed and applied for through normal channels.

Comment 3

[:shell escalante]

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.

Comment 4

[Dan Mosedale (:dmosedale, :dmose)]

[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.

Comment 5

[Dan Mosedale (:dmosedale, :dmose)]

Never mind; was thinking of bug 1124381.

Comment 6

[Dan Mosedale (:dmosedale, :dmose)]

(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.

Comment 7

[Mark Banner (:standard8)]

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