Closed Bug 1029265 Opened 11 years ago Closed 11 years ago

Breakdown -- Search Test: Design spike; change notification

Categories

(Firefox :: Search, defect)

Product:
Firefox
Component:
Search
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1029189

People

(Reporter: chadw, Unassigned)

References

Details

Story: As a product owner I want to know how letting users know that we are changing their default search provider impacts their default preference and search behavior so that I can refine our messaging strategy. Acceptance Criteria: *Cells 3 and 5 will see a notification that we have changed their default provider *The notification should be brief and remind users that they have a choice in their default provider *The notification should link to a Sumo page explaining how to change search defaults
Flags: firefox-backlog+
QA Whiteboard: [qa-]
Whiteboard: [ux]
Assignee: nobody → philipp
Status: NEW → ASSIGNED
Iteration: --- → 33.2
Points: --- → 1
Depends on: 1029189
No longer depends on: 1029189
Not sure how that got reset
Depends on: 1029189
All the design work has already been done in bug 1029189.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Assignee: philipp → nobody
Iteration: 33.2 → ---
Points: 1 → ---
QA Whiteboard: [qa-]
Flags: firefox-backlog+ → firefox-backlog-
Whiteboard: [ux]
You need to log in before you can comment on or make changes to this bug.