Opened 12 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


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 12 years ago by Chris Nelson

Status: newassigned

I have some major scheduling revisions that I hope to push soon. I believe they will address this concern.

comment:2 Changed 12 years ago by Chris Nelson

(In [11419]) Add resource leveling to scheduler. Refs #9833, #9042, #9290, #9300, #9691, #9784.

This is rather naive. It makes sure a resource isn't doing two things at once but doesn't yet handle priorities when conflicts occur.

comment:3 Changed 12 years ago by Chris Nelson

(In [11422]) Add task sorter interface. Refs #9833, #9042, #9290, #9300, #9691, #9784.

comment:4 Changed 12 years ago by Chris Nelson

(In [11423]) Add simple task sorter. Refs #9833, #9042, #9290, #9300, #9691, #9784.

This sorts by Trac's built-in priority field (after converting the priority strings to integers).

comment:5 Changed 12 years ago by Chris Nelson

(In [11424]) Implement prioritized scheduling. Refs #9833, #9042, #9290, #9300, #9691, #9784.

This is orthogonal to resource leveling. That is even if resource leveling is disabled, this schedules the tasks for a resource using the configured sorting rule.

comment:6 Changed 12 years ago by Chris Nelson

(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 k3erg

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.

Modify Ticket

Change Properties
Set your email in Preferences
as assigned The owner will remain Chris Nelson.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.