Closed
Bug 1371239
Opened 7 years ago
Closed 4 years ago
[Creditcard Autofill] Collect information on how many users save creditcard information
Categories
(Toolkit :: Form Autofill, enhancement, P2)
Tracking
()
RESOLVED
DUPLICATE
of bug 1647380
People
(Reporter: steveck, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [form autofill] [autofill-metrics])
User Story
Product Owner should be able to see how many users saved creditcard information.
Product Owner should be able to see how many users saved creditcard information. It could be a boolean or integer if we want to record the information about the number of the creditcard profile for a single user.
Reporter | ||
Updated•7 years ago
|
Assignee: nobody → schung
Reporter | ||
Updated•7 years ago
|
Whiteboard: [story][form autofill:M4][autofill-metrics] → [story][form autofill:M4][autofill-metrics][ETA:8/4]
Reporter | ||
Comment 1•7 years ago
|
||
Hi Cindy, I moved this one out of MVP since the address one(bug 990203) is not in MVP as well. We've discussed this metrics previously and you agreed that it's not a high priority item. Please let me know if we still need it for MVP, otherwise we can implement it in V2.
Flags: needinfo?(chsiang)
Whiteboard: [story][form autofill:M4][autofill-metrics][ETA:8/4] → [story][form autofill][autofill-metrics]
Yes we agreed that this is not a high priority telemetry
Flags: needinfo?(chsiang)
Updated•7 years ago
|
Component: Form Manager → Form Autofill
Updated•4 years ago
|
Priority: -- → P2
Updated•4 years ago
|
Assignee: steveck324 → nobody
Updated•4 years ago
|
Whiteboard: [story][form autofill][autofill-metrics] → [cc-autofill-mvp] [form autofill] [autofill-metrics]
Comment 3•4 years ago
|
||
Covers 'User elects to save a credit card though the capture doorhanger' from the telemetry spreadsheet.
Updated•4 years ago
|
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
Updated•4 years ago
|
Whiteboard: [cc-autofill-mvp] [form autofill] [autofill-metrics] → [form autofill] [autofill-metrics]
You need to log in
before you can comment on or make changes to this bug.
Description
•