From the spec: > The Account Activity subpage lists all of an account’s activity on > the Marketplace, including apps/add-ons purchased, collections created, > account updates, refunds requested and actions, and other relevant > activity. A user’s activity also includes any reviewer/admin actions > taken, such as reviewing an app or restricting another user’s account. > > As we’ll now have more personal information available, any time an > account is looked up using the tool, a log should be made in the account > activity for both the admin and the user. We already record most (all?) of this stuff and Andy wrote a quick and dirty viewer which you can see at https://addons.mozilla.org/en-US/admin/models/editors/eventlog/ This bug is for: - Creating the activity page, URL at /:lang/users/:username/activity - This page is restricted to people in the Staff and Support Staff groups - Anytime the page is viewed it gets logged (see above quoted spec) - Add link to this page on the menu from bug 753979 spec: https://docs.google.com/document/d/1WX_Qis2qBDw3zrUSSmfmHSH2wZ4o-zAz2diD0wbovDA/edit?pli=1
The log https://addons.mozilla.org/en-US/admin/models/editors/eventlog/ is a port of the remora stuff and is meant to show site configuration changes within the site as an "audit trail". To be honest, I'd like to see this gone. There's also a log for developers (apps/amo/logs.py) that logs addons uploaded, new versions etc. I think we shouldn't be using the first, we should be using the second log. The log events should be then tagged as "user viewable", "admin only" etc as appropriate. I think a log showing me what I bought, or when I requested refunds is perfectly reasonable for me or admins to see.
Assignee: nobody → kumar.mcmillan
Target Milestone: --- → 2012-05-24
Assignee: kumar.mcmillan → nobody
Target Milestone: 2012-05-24 → ---
Assignee: nobody → ashort
Status: NEW → ASSIGNED
Davor, ashort is your man for the backend here
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Target Milestone: 2012-07-05 → 2012-06-21
You need to log in before you can comment on or make changes to this bug.