Opened 13 years ago
Last modified 12 years ago
#9833 assigned defect
Scheduling Ignores Milestones
Reported by: | Robert Inder | Owned by: | Chris Nelson |
---|---|---|---|
Priority: | high | Component: | TracJsGanttPlugin |
Severity: | major | Keywords: | |
Cc: | mike.kronenberg@… | Trac Release: | 0.12 |
Description
When scheduling as late as possible, tasks should be scheduled to complete no later than their milestone. Currently, it seems to be ignored, so that tasks are sometimes scheduled to (start and) finish after their milestone.
Obviously, if the milestone has no date, or a successor has an earlier "latest start date", or a parent has an earlier finish date, then that should take priority.
Attachments (0)
Change History (7)
comment:1 Changed 13 years ago by
Status: | new → assigned |
---|
comment:2 Changed 13 years ago by
comment:3 Changed 13 years ago by
comment:4 Changed 13 years ago by
comment:5 Changed 13 years ago by
comment:6 Changed 13 years ago by
(In [11426]) A tree-aware task sorter. Refs #9833, #9042, #9290, #9300, #9691, #9784.
A task's priority depends on its parent's priority.
Includes a base sorter class to hold common sorter methods.
SimpleSorter and ProjectSorter derive from the base class.
(Copy effective priority list, just in case.)
Also remove unneeded debugging output. Refs #9648.
comment:7 Changed 12 years ago by
Cc: | mike.kronenberg@… added; anonymous removed |
---|
Just putting myself on the Cc.
I, too, am very much interested in having the tickets scheduled(asap) roughly just by milestone date and ticket estimate (for planning)/finish date(for update scheduling).
This would really help us with planning instead of only documenting. Right now I end up with having tickets way after milestones. I checked out from svn yesterday, so it should be rev. 11441.
If I need correcting with my setup :) or You could use another tester, just let me know.
I have some major scheduling revisions that I hope to push soon. I believe they will address this concern.