Dependencies from MasterTickets not handled correctly for "goal="

[Chris Nelson]

If ticket 1 is required for 2 and 3 and ticket 3 has a Gantt with "goal=self", ticket 1 doesn't show up.

MasterTickets doesn't create a real relation, at least not in ticket_custom. There I see entries like:

    165 | blocking | 166, 167
    166 | blocking | 167
    168 | blocking | 167, 169

So the query which does:

            cursor.execute("SELECT t.id "
                           "FROM ticket AS t "
                           "LEFT OUTER JOIN ticket_custom AS p ON "
                           "    (t.id=p.ticket AND p.name='%s') "
                           "WHERE p.value IN (%s)" % 
                           (field, n_list))
            nodes = ['%s' % row[0] for row in cursor] 

can't work. I either need a like query or to query the master tickets table.

[Chris Nelson]

I need to add relation= to the documentation.

[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.

[Chris Nelson]

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

[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).

[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.

[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.