Closed Bug 1014435 Opened 10 years ago Closed 9 years ago

[admin] Show the duration (time taken) by the user for a task to complete

Categories

(Mozilla QA Graveyard :: One and Done, defect, P3)

Version 2
defect

Tracking

(Not tracked)

VERIFIED FIXED
Future

People

(Reporter: whimboo, Unassigned)

References

()

Details

We would like to know if our estimate for the time needed to accomplish a task is correct. Therefore I would request the display of the duration on the task attempt page. It would be great to see that in the list, and the detail report.

https://oneanddone.mozilla.org/admin/tasks/taskattempt/
https://oneanddone.mozilla.org/admin/tasks/taskattempt/343/
It might be good to also have a separate page for each task, which lists the entries it has been executed, and reports the current mean value for all tests, given by a date range.
We are not currently collecting that information (the actual time it took to complete a task) so adding that as a requirement would be step 1. While I see it being useful from a task author's perspective, I'm not sure how well it would be received by the users of the system. It would mean asking them to:

a) Keep track of how long it took them to complete a task, and
b) Reporting that time via the feedback form, or some other mechanism

Currently we are not asking them to do a, and when completing a task it can be as simple as clicking a button and then a link. They are not required to provide feedback so we would be adding a step to the "Complete a task" workflow.

I am not suggesting that we shouldn't add this for the above reasons, but I think we need to consider and discuss them.

Liz / Rebecca: What do you think?
Flags: needinfo?(rbillings)
Flags: needinfo?(lhenry)
Right now users can close a task after days- but that doesn't necessarily represent how long the task took. Adding a manual way to do that would be a low priority for me.

The time it took from start to finish is already in the tool- and visible within /admin. If there is an easy way to export this data I wouldn't oppose it after v2.0 comes out.
Flags: needinfo?(rbillings)
Where is it visible? I only see the last modified time.
https://oneanddone.mozilla.org/admin/tasks/taskattempt/

There will be one line item for Started & one for Finished for each task a user has taken. The UI isn't ideal, but the data is there.
Then your comment 'is already in the tool- and visible within /admin' was a bit misleading. But thanks for clarifying. :)
I'm not sure that's accurate Rebecca. I think each attempt will only appear once with a status of either Started, Finished or Abandoned. We do have the data in the database, which has both a creation date and a modification date for each attempt, but I don't think that information is visible via the admin screen.
Henrik: 

I like the idea of having that kind of feedback from users. But it could also potentially make people feel self-conscious about how long a task took them. I'd like to consider whether to add this or not for next quarter (since we're already prioritizing several other structural changes and adding features) 

I like your second suggestion a lot. Eventually I'd like to have the task page show the list of others who have completed (or are working on) a task, which should be possible once we have public profiles.   This could encourage people to talk with each other in IRC, for example, if they see others who have done the same task. It also is interesting from the task creator's point of view.
Flags: needinfo?(lhenry)
Moving into V2 milestone 2 as a low priority. Specifically it would be add a completion time to the Task Attempt data based on how long it took the user to click 'complete'- and is not a manual evaluation of the length it took the user. 

I agree that getting feedback from the user about the length of the task is important. The idea of how best to do that will evolve- it will be improved once we are able to contact users.
Priority: -- → P4
Target Milestone: --- → Milestone 2
Version: unspecified → Version 2
This is being done inside of https://bugzilla.mozilla.org/show_bug.cgi?id=1030767 on the Task Activity dashboard- it isn't on the task detail page, but the data will be available. Check it out:
https://wiki.mozilla.org/QA/OneandDone/v2.2_wireframes#Admin_Task_Dashboard

If you think it also should display on the Task page, leave a comment.
Rebecca, as the automatic version of this (no extra data from the user) is being covered by bug 1030767, I suggest we move this bug out of Milestone 2 and keep it around to consider in the future the idea of asking users how long it took them to complete a task. That's definitely not going to happen in this milestone.
Flags: needinfo?(rbillings)
Moved out of milestone 2, this will be left open for a future feature suggestion of getting user feedback for time completed.
Flags: needinfo?(rbillings)
Target Milestone: Milestone 2 → Future
This will require:
- on the create task page, add open text field next to time estimate radio buttons that only accepts whole numbers
Whiteboard: [goodfirstbug]
Sorry- ignore my comments I was on the wrong tab :/
Whiteboard: [goodfirstbug]
This will require:
- On the completed task thank you page add an optional text field
- Text "How many minutes did the task take to complete?"
- Allow room for at least 5 digits
Priority: P4 → P3
assigned:nobody->tessyjoseph1992@gmail.com
Commits pushed to master at https://github.com/mozilla/oneanddone

https://github.com/mozilla/oneanddone/commit/17455bc54d5af9a57efdf43ee414193cd5c38584
Fix Bug 1014435 - [admin] Show the duration (time taken) by the user for a task to complete

https://github.com/mozilla/oneanddone/commit/39a00846533172c64b534dcfded086446c514f36
Merge pull request #245 from tessie/featureBug1014435

Fix Bug 1014435 - [admin] Show the duration (time taken) by the user for a task to complete
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Verified field - and errors and email response on staging
Verified on prod
Status: RESOLVED → VERIFIED
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.