Closed Bug 1155112 Opened 9 years ago Closed 8 years ago

Disconnect the link clicker as the link generator leaves the conversation

Categories

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

defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: RT, Unassigned)

References

Details

User Story

As a link clicker, I want to be disconnected from the conversation when the link generator leaves the conversation so that I can't leave my camera running without noticing.

Acceptance criteria:
* When a link clicker is in a conversation, if the link generator leaves first intentionally, disconnect the link clicker automatically and prompt him an informational message about what happened with an option to rejoin:

The other person has left the conversation.
[Rejoin]

* When a link clicker is in a conversation, if the link generator leaves first non intentionally (network error or other), disconnect the link clicker automatically and prompt him an informational message about what happened with an option to rejoin:

An error occurred and you were both disconnected from the conversation.
[Rejoin]
As a link clicker, I want to be disconnected from the conversation when the link generator leaves the conversation so that I can't leave my camera running without noticing.

Acceptance criteria:
* When a link clicker is in a conversation, if the link generator leaves first, disconnect the link clicker automatically 
* When disconnected the link clicker is taken to the same page as if he had disconnected himself.
Blocks: 1125082
Sevaan, does this look right in terms of experience?
Flags: needinfo?(sfranks)
Thumbs up from me.
Flags: needinfo?(sfranks)
Shell, this feels like a high value/low effort bug. Maybe a good first bug?
Flags: needinfo?(sescalante)
talked with gavin - not "good first bug" (easy for new, outside devs to take) P2?

Dan, can you get an estimate how hard this would be?  If it's a fairly simple bug - it would have a good impact to a confusing user scenario.
Rank: 29
Flags: needinfo?(sescalante)
Flags: needinfo?(dmose)
Flags: firefox-backlog+
Priority: -- → P2
Whiteboard: [link-clicker]
I think we're missing part of the user story here.

RT:

- what should the UX be if the remote peer is disconnected due to a network issue or something?
- Do we want any message other than just "How was your conversation?" ?
Flags: needinfo?(dmose) → needinfo?(rtestard)
(In reply to Mark Banner (:standard8) from comment #5)
> I think we're missing part of the user story here.
> 
> RT:
> 
> - what should the UX be if the remote peer is disconnected due to a network
> issue or something?
> - Do we want any message other than just "How was your conversation?" ?

Fair point, seems like we need to cover these scenarios more appropriately.
I added these as acceptance criteria to the bug.
Matej/Sevaan can you please help regarding the messaging to the user in these scenarios?
User Story: (updated)
Flags: needinfo?(sfranks)
Flags: needinfo?(rtestard)
Flags: needinfo?(matej)
Here are some options for both:


* When a link clicker is in a conversation, if the link generator leaves first intentionally, disconnect the link clicker automatically and prompt him an informational message about what happened (MESSAGE 1 TBD) with an option to rejoin.

The other person left the conversation and you were automatically disconnected. [Rejoin] [Cancel]

The other person has left the conversation. Would you like to rejoin? [Yes] [No]

You have automatically left the conversation because the other person disconnected. [Rejoin] [Cancel]


* When a link clicker is in a conversation, if the link generator leaves first non intentionally (network error or other), disconnect the link clicker automatically and prompt him an informational message about what happened (MESSAGE 2 TBD) with an option to rejoin.

An error occurred and you were both disconnected from the conversation. [Rejoin] [Cancel]

The other person experienced an error and you were automatically disconnected. [Rejoin] [Cancel]

You have automatically left the conversation because the other person experienced an error. [Rejoin] [Cancel]
Flags: needinfo?(matej)
I like: 

> The other person has left the conversation. Would you like to rejoin? [Yes]
> [No]

> * When a link clicker is in a conversation, if the link generator leaves
> first non intentionally (network error or other), disconnect the link
> clicker automatically and prompt him an informational message about what
> happened (MESSAGE 2 TBD) with an option to rejoin.
> 
> An error occurred and you were both disconnected from the conversation.
> [Rejoin] [Cancel]
> 

I don't think we need a 'No' or 'Cancel' button though. Just a button that says "Rejoin" should suffice.
Flags: needinfo?(sfranks)
+1 to Sevaan's comments.
I amended the US to reflect this.
User Story: (updated)
Rank: 29 → 22
Assignee: nobody → dmose
Iteration: --- → 42.1 - Jul 13
Rank: 22 → 30
Priority: P2 → P3
Iteration: 42.1 - Jul 13 → 42.2 - Jul 27
Iteration: 42.2 - Jul 27 → 42.3 - Aug 10
Assignee: dmose → nobody
Iteration: 42.3 - Aug 10 → ---
Whiteboard: [link-clicker]
Support for Hello/Loop has been discontinued.

https://support.mozilla.org/kb/hello-status

Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.