Browser client (websocket) logins not tracking user activity
Bug #1818153 reported by
Bill Erickson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
High
|
Unassigned | ||
3.1 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Evergreen 3.2
Logins to the staff client are not represented as rows in actor.usr_activity. This is a result of missing config.
Proposal is to add 4 new activity types:
ewhat login, ehow ws-translator-v1
ewhat login, ehow ws-translator-v2
ewhat login
ewhat verivy
The latter 2 ensure that new ingress options are represented going forward even when new activity types are not specifically added for them.
Changed in evergreen: | |
milestone: | 3.2.4 → 3.2.5 |
Changed in evergreen: | |
assignee: | nobody → Michele Morgan (mmorgan) |
Changed in evergreen: | |
assignee: | Michele Morgan (mmorgan) → Bill Erickson (berick) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
And ws-translator-v* 'verify' entries.