You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Request is to have a task where we can set the amount of work for that task.
However this task will not have a start and end date because it is a ongoing
task Meaning that it is something that we do if we have spare time.
Also we may have more then one contributor for a single task.
Once the amount of time for this task is consume, a visual cue will be display.
Original issue reported on code.google.com by lucp9...@gmail.com on 2 Nov 2011 at 12:43
The text was updated successfully, but these errors were encountered:
Yep just like I mention to you
I'm involved in a project where we have defined 200 men-hours inside a
project of 2000. Those 200 men-hours will be made by several people during
the project (200 men-hours to be done during a six month project)
Those 200 men-hours are to produce documentation as the project evolves.
We also require floating task that will float in the Gantt chart until we
hit start. I did not mention this type of task in my request but since you
are here :-)
The starting for this task is the Today's date. Once the start button is
hit, the start date is anchor but the end date is floating.
So if we have schedule 20 days floating, once we hit start, the start date
is anchor...twenty days later, if not all the hours/days have been register,
the end is move back to the Today's date until we it finish or all the
hours/days are register. Even then if all the men-hours are register but
more are add, the end date will be push back allowing the final date of the
project to be push back to.... Only the stop task will fix the end date
I know it is a weird concept but it has its application...
Original comment by lucp9...@gmail.com on 3 Nov 2011 at 10:38
Original issue reported on code.google.com by
lucp9...@gmail.com
on 2 Nov 2011 at 12:43The text was updated successfully, but these errors were encountered: