Closed
Bug 486605
Opened 17 years ago
Closed 17 years ago
Track number of e-mail shares
Categories
(addons.mozilla.org Graveyard :: Collections, defect, P1)
addons.mozilla.org Graveyard
Collections
Tracking
(Not tracked)
RESOLVED
FIXED
BW-M5
People
(Reporter: fligtar, Assigned: wenzel)
Details
Attachments
(2 files)
|
140 bytes,
text/plain
|
Details | |
|
2.34 KB,
patch
|
lorchard
:
review+
|
Details | Diff | Splinter Review |
We should track the total number of times each add-on has been shared via email. We don't need to expose this anywhere quite yet, but the next phase of bandwagon will have a lot more stats information and we can expose it then.
| Reporter | ||
Updated•17 years ago
|
Priority: -- → P1
Updated•17 years ago
|
Assignee: nobody → fwenzel
| Assignee | ||
Comment 1•17 years ago
|
||
We need a new counter field.
| Assignee | ||
Comment 2•17 years ago
|
||
This saves the share count on email submission. Note that it counts the *recipients*, not the times somebody uses the the sharing function. Fligtar, if that's not what you wanted, speak up.
Attachment #372833 -
Flags: review?(lorchard)
| Assignee | ||
Updated•17 years ago
|
Status: NEW → ASSIGNED
Updated•17 years ago
|
Attachment #372833 -
Flags: review?(lorchard) → review+
Comment 3•17 years ago
|
||
Comment on attachment 372833 [details] [diff] [review]
Save share count
No test case, but it worked for me!
| Assignee | ||
Comment 4•17 years ago
|
||
(In reply to comment #3)
> (From update of attachment 372833 [details] [diff] [review])
> No test case, but it worked for me!
Hm, looks like we need an actual unit test for this. As the data is not available through the API (yet, anyway), I can't see from the outside if it worked :-/.
| Reporter | ||
Comment 5•17 years ago
|
||
Moving to revised M5 milestone (4/28).
Target Milestone: BW-M4 → BW-M5
| Assignee | ||
Comment 6•17 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•