GitLab

in the future, we migrate js/css files to RT 4's structure.

see also
http://weblog.bulknews.net/post/33907905561/do-not-ship-modules-with-module-install-1-04

and http://cpansearch.perl.org/src/ADAMK/Module-Install-1.06/Changes

before taking the first parent, we should check if there is parent exists
in the previous rows, and if there is, we should use that instead.

consider:

4 has 1 child: 1
1 has 2 parents: 3 and 4

if we get chart via ?Ticket=4, then we probably want 4 as the parent of 1
instead of 3.

the default one is already pretty imo

everyone loves coloring owners consistently

linear "push @tickets, $ticket" is wrong, here is an example:
12 has 1 children: 13
12 has 2 parents: 10 and 3
3 has 2 children: 5 and 12

to get all related tickets of 12, let's see how @tickets change in old way:

(10,3) # initial
(10,3,12) # after searching ticket 10
(10,3,12,5) # after searching ticket 3
(10,3,12,5,13) # after searching ticket 12

aparently, 5(child of 3) should appear right after 3 insetad of 12,
while 13(children of 12) should appear right after 12

so we can just call @tickets = _GetOrderedTickets(...);

so if it's not the first parent, folder doesn't work.
here we make a more strict "has_members" testing to avoid invalid "folder" chars

in previous versions, members may be shown far away from parents
this only works for queries like /Search/JSGantt.html?Ticket=12

see also http://code.google.com/p/jsgantt/issues/detail?id=54