Closed Bug 1118833 Opened 10 years ago Closed 10 years ago

[User story] As a link clicker in a conversation, I want to see any contextual information associated with the conversation so that I am better prepared and more engaged when I join.

Categories

(Hello (Loop) :: Client, enhancement, P2)

Product:
Hello (Loop)
Component:
Client
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Blocking Flags:
backlog backlog+

People

(Reporter: RT, Unassigned)

References

(
URL
)

Details

(Whiteboard: [context])

User Story

As a link clicker in a conversation, I want to see any contextual information associated with the conversation so that I am better prepared and more engaged when I join.

UX: https://bug1115340.bugzilla.mozilla.org/attachment.cgi?id=8568131

Acceptance criteria:
* When in a conversation or out of a conversation, the following details about the attached URL get displayed to the link clicker on the right hand side of the screen:
- Thumbnail and favicon of the webpage the URL points to
- Content of the <title> tag of the webpage the URL points to
- URL
* Clicking the URL opens the URL in a new tab
* Accessing the URL from the standalone client will trigger a GA event

Attachments

(1 obsolete file)

No description provided.
Blocks: 1115340
backlog: --- → Fx38+
User Story: (updated)
Summary: [meta] As a link clicker in a conversation, I want to access a URL context supporting the conversation so it's more convenient. → [User story] As a link clicker in a conversation, I want to access a URL context supporting the conversation so it's more convenient.
backlog: Fx38+ → Fx38?
User Story: (updated)
Summary: [User story] As a link clicker in a conversation, I want to access a URL context supporting the conversation so it's more convenient. → [User story] As a link clicker in a conversation, I want to see any contextual information associated with the conversation so that I am better prepared and more engaged when I join.
User Story: (updated)
Attached image 3.png (obsolete) —
Attaching Sevaan's design
putting at P5 as it's actively being worked in PM and the creative team to prioritize co-browsing scenarios. it's not actionable to put as higher priority until the scenarios and prioritization and UX are finalized.
Priority: -- → P5
backlog: Fx38? → Fx39+
blocked on work happening with ckarloff's team now... but will be next highest feature priority.
backlog: Fx39+ → Fx38+
Rank: 30
Priority: P5 → P3
User Story: (updated)
User Story: (updated)
User Story: (updated)
backlog: Fx38+ → backlog+
Rank: 30 → 22
Flags: firefox-backlog+
Priority: P3 → P2
Whiteboard: [context]
Attachment #8546567 - Attachment is obsolete: true
URL: https://bug1115340.bugzilla.mozilla.o...
User Story: (updated)
Severity: normal → enhancement
(Commenting on User Story) > * Accessing the URL from the standalone client will trigger a Telemetry event Romain: This isn't possible - we might not be in Firefox and we won't be able to tie up the data. My best thought would be that analytics would give us this data.
Flags: needinfo?(rtestard)
Depends on: 1142588
(In reply to Mark Banner (:standard8) from comment #4) > (Commenting on User Story) > > * Accessing the URL from the standalone client will trigger a Telemetry event > > Romain: This isn't possible - we might not be in Firefox and we won't be > able to tie up the data. My best thought would be that analytics would give > us this data. Thanks, makes total sense. I changed the user story accordingly and added a GA field on bug 1132222 to track this. 2 questions though: - Will we be able to use Google analytics from the desktop client UI when link clickers on the desktop client UI access URLs? - I marked bug as a dependency of this bug although it includes more GA events then just the one we talk about here. Does it make sense to address all the GA events at once or do you prefer a separate bug to track the specific GA event required here?
Depends on: 1132222
Flags: needinfo?(rtestard)
User Story: (updated)
Dependent bugs have landed -> fixed.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: