Closed
Bug 1107239
Opened 10 years ago
Closed 8 years ago
Disallow users to mark a task as complete within x seconds of a threshold
Categories
(Mozilla QA Graveyard :: One and Done, defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
Future
People
(Reporter: bsilverberg, Assigned: bsilverberg)
Details
There is currently a bunch of logic in One and Done to deal with the fact that people can take a task and then mark it as complete immediately, but we do not really consider those to be complete tasks. This logic is in place to try to make the metrics more accurate by ignoring those attempts, but a better approach would be to not allow users to mark a task as complete within the threshold. This bug includes: - Disable the "Complete" button for x seconds after an attempt has been started. - Add logic to prevent a task from being marked as complete within the threshold, in case a user gets around the UI. - Remove all logic that currently deals with these "fake" attempts by checking the time between task start and end. This would include functions to support metrics as well as the "Too Short" tasks report. Note that once this is complete we will no longer be ignoring the "grandfathered" invalid complete attempts. They will now be included in metrics, but will affect the metrics less and less as more and more attempts are added with the new logic in place.
Comment 1•10 years ago
|
||
This can be discussed in our next meeting [12/17/14] or via email. At minimum it should be disabled for 60 seconds.
Comment 2•9 years ago
|
||
We should do some investigation to see what amount of time people are finishing tasks in a way that abuses the system. Is it 30 seconds or 60 seconds? Goal is to prevent adding bad data to metrics. Need also to investigate how this would be done- how will the complete button be re-enabled if the user is just sitting on the page.
Priority: P2 → P3
Comment 3•8 years ago
|
||
Closing as won't fix. We don't want to make the site look broken & users will do what they will. There is no real benefit to implementing this at this time.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•