Feature #535

Feature #540: GWT: x.x, activity log

GWT: x.x, upgrade subscription logs

Added by Matthieu Decorde almost 6 years ago. Updated almost 6 years ago.

Status:Closed Start date:01/22/2014
Priority:High Due date:
Assignee:- % Done:

100%

Category:- Spent time: -
Target version:Portal 0.6 Estimated time:0.50 hour

Description

- Allow admin to have quick access to subscription logs
- log failure and success (right now only the subscription request is logged)

History

#1 Updated by Matthieu Decorde almost 6 years ago

  • Parent task set to #540

#2 Updated by Alexey Lavrentev almost 6 years ago

  • Target version changed from Portal X.X to Portal 0.6

#3 Updated by Matthieu Decorde almost 6 years ago

  • Estimated time set to 0.50

#4 Updated by Alexey Lavrentev almost 6 years ago

  • Priority changed from Normal to High

#5 Updated by Matthieu Decorde almost 6 years ago

  • % Done changed from 0 to 80

#6 Updated by Matthieu Decorde almost 6 years ago

  • Status changed from New to Resolved

#7 Updated by Alexey Lavrentev almost 6 years ago

  • Status changed from Resolved to Feedback
  • % Done changed from 80 to 70
OK: New log entries created:
  • activateAccount
  • activateAccount-complete
Not OK:
  • The sign-up form completion generates an entry with the user ID in "level" column.
  • Should be
    • "askAccessAndSubscribe" in the "level" comumn
    • the newly created login should appear either in the login column or as a parameter together with the email address
  • the action column always shows "0". Is it useful?

#8 Updated by Alexey Lavrentev almost 6 years ago

  • Priority changed from High to Normal

#9 Updated by Matthieu Decorde almost 6 years ago

  • % Done changed from 70 to 90

fix: the "level" column
fix: column order (same bug as ticket #537)
add: login to command parameter

The "level" values are:
  • 0: went well
  • 1: permission fail
  • 2: Java error

#10 Updated by Alexey Lavrentev almost 6 years ago

OK on test portal.

Note that the level is "0" even if the sign-up failed (wrong captcha, email already used...)

#11 Updated by Alexey Lavrentev almost 6 years ago

  • Priority changed from Normal to High

#12 Updated by Alexey Lavrentev almost 6 years ago

  • Status changed from Feedback to Resolved

#13 Updated by Alexey Lavrentev almost 6 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 90 to 100

OK on BFM portal

Also available in: Atom PDF