Open
Bug 1474481
Opened 7 years ago
Updated 6 months ago
Support Forum Metrics Dashboard does not work, blank
Categories
(support.mozilla.org :: Questions, defect, P1)
support.mozilla.org
Questions
Tracking
(Not tracked)
NEW
People
(Reporter: guigs, Unassigned)
References
Details
https://support.mozilla.org/en-US/questions/dashboard/metrics
I think this also has to do with the outdated ElasticSearch of the current instance of kitsune on AWS according to Bug 1262944, however I am not sure if this is for all dashboards.
I am filing this bug for this use case:
As a contributor I would like to be able to see my impact on the volume of questions asked each day in the forum.
As a community manager, I would like to be able to see the progress of the number of questions that are answered, unanswered, solved, and if there is an increase or decrease in the # questions over a 24 hour period, 72 hour period, and for all time (month, week, year)
This is a core feature for gamification in the forums to encourage users to participate more and is a core function for metric reporting for the support communities impact for Mozilla as a whole.
Please fix this soon.
| Reporter | ||
Updated•7 years ago
|
Severity: normal → major
Priority: -- → P1
Comment 1•7 years ago
|
||
I'm running a reindex of elasticsearch now. Hopefully this will fix it. After that I'll look into why it got into this state.
Comment 2•7 years ago
|
||
Clearly that did not fix it. Still investigating. I think you're right that it must have to do with our use of outdated ElasticSearch and libraries. I think this is likely affecting a number of dashboards. I'm hopeful that we can fix these with some upgrades in the near term, and then hopefully move these to a better and more comprehensive dashboard solution after that.
I appreciate your patience with me as I ramp up on my understanding of the code in these various ares of the site.
Updated•2 years ago
|
See Also: → https://github.com/mozilla/sumo/issues/1207
Updated•2 years ago
|
Type: task → defect
You need to log in
before you can comment on or make changes to this bug.
Description
•