Closed
Bug 452829
Opened 17 years ago
Closed 17 years ago
Implement CSAT support for Knowledge Base
Categories
(support.mozilla.org :: Knowledge Base Software, task, P1)
support.mozilla.org
Knowledge Base Software
Tracking
(Not tracked)
VERIFIED
FIXED
0.7
People
(Reporter: laura, Assigned: nkoth)
References
Details
(Whiteboard: tiki_feature, tiki_discuss)
Attachments
(5 files, 4 obsolete files)
|
13.31 KB,
patch
|
laura
:
review+
|
Details | Diff | Splinter Review |
|
36.73 KB,
image/png
|
Details | |
|
41.64 KB,
image/png
|
Details | |
|
29.53 KB,
patch
|
laura
:
review+
|
Details | Diff | Splinter Review |
|
9.09 KB,
patch
|
laura
:
review+
|
Details | Diff | Splinter Review |
As per https://wiki.mozilla.org/Support:CSAT:
* Update db to support CSAT (including new CSAT tables and updating existing user tables)
* Implement AJAXified popup of survey when someone clicks Yes on poll "Did this article solve a problem you had with Firefox?" in the KB.
| Reporter | ||
Updated•17 years ago
|
Priority: -- → P1
| Assignee | ||
Comment 1•17 years ago
|
||
Attachment #338267 -
Flags: review?(laura)
| Assignee | ||
Comment 2•17 years ago
|
||
the rest of the bug is in progress, but creating new tables first.
| Reporter | ||
Comment 3•17 years ago
|
||
Comment on attachment 338267 [details] [diff] [review]
Is the default charset and innodb correct?
The tables look good to me except that our other tables are all latin1, so these should be too I'm assuming.
Attachment #338267 -
Flags: review?(laura) → review-
Comment 4•17 years ago
|
||
Nelson, could we get an update on this please?
| Reporter | ||
Updated•17 years ago
|
Target Milestone: 0.6.4 → 0.7
| Assignee | ||
Updated•17 years ago
|
Attachment #338267 -
Attachment is obsolete: true
| Assignee | ||
Comment 5•17 years ago
|
||
Attachment #340097 -
Flags: review?(laura)
| Assignee | ||
Comment 6•17 years ago
|
||
Attachment #340098 -
Flags: review?(laura)
| Assignee | ||
Comment 7•17 years ago
|
||
| Assignee | ||
Comment 8•17 years ago
|
||
| Assignee | ||
Comment 9•17 years ago
|
||
Outstanding issues to be fixed shortly (in the next 24 hours):
1) Answering "No" to "Did this article solve a problem you had with Firefox?" currently also gives the CSAT question. It should not.
2) Need admin panel to allow changing of text of question.
3) Need some modifications to existing poll results reporting page to make it work again.
4) Need some sample db scripts to be run offline to generate statistics.
5) Hide the "ratings" box on the edit UI - it is not necessary anymore.
| Reporter | ||
Comment 10•17 years ago
|
||
Comment on attachment 340098 [details] [diff] [review]
This is the PHP script to upgrade the database
Point the connect string at db/local.php so this will work on stage/prod, otherwise good. It's going to take a little time to run so will require downtime.
Attachment #340098 -
Flags: review?(laura) → review+
| Reporter | ||
Comment 11•17 years ago
|
||
Comment on attachment 340097 [details] [diff] [review]
This is the patch for functionality needed to collect data
Let's switch to POST rather than REQUEST as I'd like to phase out use of REQUEST. Otherwise WFM.
Attachment #340097 -
Flags: review?(laura) → review+
| Reporter | ||
Comment 12•17 years ago
|
||
I think djst is going to have different question wording as well, just heads up.
| Assignee | ||
Comment 13•17 years ago
|
||
Attachment #340098 -
Attachment is obsolete: true
| Assignee | ||
Comment 14•17 years ago
|
||
Attachment #340211 -
Attachment is obsolete: true
Attachment #340215 -
Flags: review?(laura)
| Reporter | ||
Updated•17 years ago
|
Attachment #340215 -
Flags: review?(laura) → review+
| Assignee | ||
Comment 15•17 years ago
|
||
https://bugzilla.mozilla.org/attachment.cgi?id=340097 patch in trunk in r18573.
| Assignee | ||
Comment 16•17 years ago
|
||
Attachment #340351 -
Flags: review?(laura)
| Assignee | ||
Comment 17•17 years ago
|
||
This is the same as the previous patch with the difference that it checks that an upgrade has not been previously completed. This is to avoid upgrading twice (which will cause data loss of poll information)
Attachment #340215 -
Attachment is obsolete: true
| Assignee | ||
Comment 18•17 years ago
|
||
This part 1 patch is now in production branch r18620.
(In reply to comment #15)
> https://bugzilla.mozilla.org/attachment.cgi?id=340097 patch in trunk in r18573.
| Reporter | ||
Comment 19•17 years ago
|
||
Comment on attachment 340351 [details] [diff] [review]
This is the patch for part 2 (incremental patch, requires 1st patch)
We probably need some docs to explain how the special CSAT polls work - please add to wiki.mozilla.org/Support somewhere.
Attachment #340351 -
Flags: review?(laura) → review+
| Reporter | ||
Updated•17 years ago
|
Attachment #340372 -
Flags: review+
| Assignee | ||
Comment 20•17 years ago
|
||
patch part 2 committed to: r18623/r18624
| Assignee | ||
Updated•17 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 21•17 years ago
|
||
Minor change to show poll title next to result when "All" is selected as the question to show results for, in r18662/r18663
| Assignee | ||
Comment 22•17 years ago
|
||
fix votes was not being recorded correctly in r18667/r18668
I'm going to verify this as fixed; we've filed a few spinoff bugs, and also have tested this quite well through its implementation. (Changes in comment 21 and comment 22 are examples, along with bug 457277 and bug 457492.)
I'll continue testing (and the team will be using it soon in production, too), so we'll continue to file bugs.
Status: RESOLVED → VERIFIED
Updated•16 years ago
|
Whiteboard: tiki_feature
Comment 24•16 years ago
|
||
Very useful tracking here. I finally begin to understand how it all ties together. Most of it can probably be upstreamed directly, but the initialization of the polls is problematic.
Here is my understanding.
Tiki used to have poll templates. Those worked nicely to generate the polls for each object. However, there was no tracking to where the poll came from. Questions add this traceability by linking all the polls relating to the same question together and allow to collect data for CSAT afterwards.
The questions apply for all objects in a given category and the polls get created when the pages enter the category. This part right now is mostly hardcoded. In fact, it's even linked to the staging feature by using it as the base category.
I would propose the following changes:
Add a categId field to the question. Because the question entry is short, I see no problem in duplicating the question if a question affects multiple categories. Probably not a frequent case anyway.
When displaying the page, it would simply obtain the list of questions that apply for it from the categories, which are already loaded. Polls attached to the object would only be displayed if they are not related to a question for backward compatibility (not used on SUMO, I would guess).
Add a pollTemplateId to the question. It would represent the relationship better. Right now, a template poll with the same question id is looked up, creating a one to many relationship rather than many to 1.
Whiteboard: tiki_feature → tiki_feature, tiki_discuss
Comment 25•16 years ago
|
||
Morgamic, can you please advice?
Comment 26•16 years ago
|
||
Just for posterity here, David and I also discussed implementing a CSAT (or somewhat friendlier-named) component that doesn't overlap with polls.
Comment 27•16 years ago
|
||
What's the status here? Louis-Philippe? Anyone else? Bueller?
Comment 28•16 years ago
|
||
Nothing moved on my side as there is no feedback.
Comment 29•16 years ago
|
||
In comment 24, you seemed to have a pretty good start on an upstream implementation. Did that get into tiki's trunk?
Comment 30•16 years ago
|
||
It was only a proposal. Nothing was done in trunk.
| Reporter | ||
Comment 31•15 years ago
|
||
LPH, can you explain why the implementation needs to change? Marc and I were not clear.
Comment 32•15 years ago
|
||
I'm trying to decouple the functionalities to make them usable. There are currently multiple dependencies with how SUMO is set-up. All the initialization of questions is also hard-coded, so can't be upstreamed directly.
You need to log in
before you can comment on or make changes to this bug.
Description
•