Closed Bug 969291 Opened 12 years ago Closed 12 years ago

Record who marked a question as solved

Categories

(support.mozilla.org :: Questions, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED
2014Q1

People

(Reporter: atopal, Assigned: rrosario)

Details

(Whiteboard: u=sumo-team c=questions p=1 s=2014.4)

Currently we record only that a question was marked as solved, but since moderators are marking things as solved too, it's unclear whether a question was marked as solved by a moderator or the user. We don't have to make that visible on the page, but we need a way to tell who solved a thread when querying the database for metrics. Specifically, I'd like to know what our solution rate is considering only users marking things as solved. Changes we make to any of the flows try to improve that rate for users, not for moderators, so being able to tell them apart will give us a noise free indicator of success
Specifically I'd love to see this but who would be able to see who marked the solution? Contributors? Moderators? Everybody?
I only wanted to have that in the db, but yeah, we could add a tool tip to the "chosen solution" text with the username of the person who chose it, like "Chosen as the solution by Jack"
+1 to Kadir's idea
The quick way to do this is to throw a new row in the questions_questionmetadata table. The harder way (and better?) to do this is to add a new column to the table. If we just need to display the solver on the question details page and use it for reporting, then we don't really need it to be a new column. If we want to show the solver on the question listing page, then it should be a column to avoid that extra join there (this wasn't requested in the bug). My vote is to throw it into the question metadata table for now and we can always add the column later and migrate the data. For that, I am guessing 1pt
Whiteboard: u=sumo-team c=questions p= s=2014.4 → u=sumo-team c=questions p=1 s=2014.4
Assignee: nobody → rrosario
I pushed this to prod just now.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Thanks!
You need to log in before you can comment on or make changes to this bug.