Closed
Bug 1036928
Opened 11 years ago
Closed 9 years ago
Allow to set longer time estimages as 60 minutes
Categories
(Mozilla QA Graveyard :: One and Done, defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
Milestone 2
People
(Reporter: whimboo, Unassigned)
Details
(Whiteboard: [qa-automation-wanted][good first bug])
We in the automation team want to add more tasks specifically for creating automated tests. Therefore we need a longer estimate of time, which can go up to a week. The 60s limit at the moment is a real blocker for us. Would be great if we can get this opened up.
Comment 1•11 years ago
|
||
The intention of One and Done as a tool was to provide a series of quick and easy tasks to new contributors- a way to sample QA tasks, and check out different teams. Having a task that takes longer than an hour defeats this purpose. That being said this would be better discussed in one of our meetings- please bring it up as an agenda item.
Comment 2•11 years ago
|
||
Discussed at today's meeting, adding to v2m2. Please add "60+" radio button to the Create task page. Add "60+" to the Estimated minutes checkboxes on Available Tasks and tasks/list.
Priority: -- → P3
Target Milestone: --- → Milestone 2
Version: unspecified → Version 2
Updated•11 years ago
|
Assignee: nobody → bob.silverberg
Comment 3•11 years ago
|
||
One issue we will have with implementation for this is that the execution_time (estimated time to complete) is stored as an integer, so we cannot really have a value of 60+. One approach would be to choose an arbitrary number that is greater than 60 and then program the system to recognize that as 60+, but that's really a less-than-ideal approach.
A different approach would be significantly more complicated, though, so we need to consider that fact. Can you table this for discussion at our next meeting?
Flags: needinfo?(rbillings)
Comment 4•11 years ago
|
||
I've added it to the next meeting agenda as a discussion item. I can also see how it will impact task time estimates.
Flags: needinfo?(rbillings)
Comment 5•11 years ago
|
||
Instead of adding many radio buttons, let's make this a feature to add an empty box where admins creating a task can enter the time estimate.
Updated•11 years ago
|
Status: NEW → ASSIGNED
Updated•11 years ago
|
Assignee: bob.silverberg → nobody
Status: ASSIGNED → NEW
Comment 6•11 years ago
|
||
This will require:
- on the create task page, add open text field next to time estimate radio buttons that only accepts whole numbers
Whiteboard: [qa-automation-wanted] → [qa-automation-wanted][goodfirstbug]
Comment 7•11 years ago
|
||
Rebecca, I was proposing just replacing the existing select with a text box, so the only option will be to enter a number, not to add a text box in addition to the select. Does that sound ok to you?
Flags: needinfo?(rbillings)
Comment 8•11 years ago
|
||
I would like to work on this. One question: We now have estimated time as 15,30,45,60. Do I need to add a new text area so that admin can give in their desired time limit or change the existing select with a text box like Bob suggested.
If I change the existing select with text area- then we won't be having the dropdown of 15,30,45,60 right? Can I go ahead and work on this?
Comment 9•11 years ago
|
||
Thanks for offering to work on this Jicksy. Rebecca and I discussed this briefly and I think it would be better to go with her suggestion of adding a text input in addition to the select. That way most tasks will still end up with a standard increment which will work well with the filtering we have in place. So please go ahead and work on this (I will assign it to you) with the assumption that you will be adding a text input beside the existing select input.
Assignee: nobody → jicksy.john
Status: NEW → ASSIGNED
Flags: needinfo?(rbillings)
Comment 10•11 years ago
|
||
Bob,
We will be having choices (15,30,45,60,60+)
and also a text area where admin can enter any integer. Just confirming if what I made out is correct.
Comment 11•11 years ago
|
||
Thanks for checking Jicksy. No that is not correct. It will be choices of (15, 30, 45, 60) just like now, and also a text input where an admin can enter an integer.
Comment 12•11 years ago
|
||
Bob,
I could get through the code.
I have certain doubts:
What I have done is- I created an integer field below 'estimated time' and named it 'customized time' (for now). If Admin wants to enter a time greater than 60, he can enter in this area.
If anytime Admin enters a value in this text field, then this value should over ride estimated_time- and while displaying task time it should show this manually entered time.
How will this be filtered in task filtering based on time? Should I make a clause 'Enter values more than 60 only' ?
So that in the filtering I can give a choice 60+ also, so that all those tasks that have more time than 60 will fall under that?
For a person searching for tasks with time more than 60 this should help.
Comment 13•11 years ago
|
||
Thanks for the update Jicksy. I'm not sure I fully understand what it is you have done. Could you submit a pull request so I can see the exact code? You can comment in the pull request that it is not yet complete and is only being submitted for feedback.
Comment 14•11 years ago
|
||
Comment 15•11 years ago
|
||
Ignore the previous pull request :
https://github.com/mozilla/oneanddone/pull/210
Comment 16•11 years ago
|
||
This is the current running pull request.
https://github.com/mozilla/oneanddone/pull/211
Updated•11 years ago
|
Assignee: jicksy.john → shubhamjindal18
Updated•10 years ago
|
Whiteboard: [qa-automation-wanted][goodfirstbug] → [qa-automation-wanted][good first bug]
Updated•10 years ago
|
Assignee: shubhamjindal18 → nobody
Comment 19•9 years ago
|
||
Project is being retired.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Updated•7 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
•