Keyword 'sorttasks' criteria 'tree' buggy when used with additional criteria ismilestone(plan)?

[A.Nagy]

Hi all,

I have a problem with the Keyword 'sorttasks' criteria 'tree'. I have two taskreports deinfed - one with all tasks and milestones - one only with milestones.
When I use:

...
hidetask ~(p_105_4407)
sorttasks tree
...

all is fine in my html-output file and the tasks and milestones are sorted/looks like:

MS_1
MS_2
MS_2.1
MS_2.1.1
MS_2.1.2
MS_2.2
MS_2.3
MS_2.4
MS_2.5
MS_2.6
MS_2.7
MS_3
MS_4
MS_5
MS_6
MS_7
MS_8
MS_9
TASK_1
TASK_2
TASK_3
...AND SO ON...

When I use:

...
hidetask ~(p_105_4407)  | ~(ismilestone(plan))
sorttasks tree
...

the html-output file looks like:

MS_1
MS_3
MS_4
MS_5
MS_6
MS_7
MS_8
MS_9
MS_2
MS_2.2
MS_2.3
MS_2.4
MS_2.5
MS_2.6
MS_2.7
MS_2.1
MS_2.1.1
MS_2.1.2

Somebody an idea/same problem?

Thank you very much indeed for your help!

greetings

alex

[A.Nagy]

Hi all,

for whom who is interested:

...

sorttasks tree, name.up
    hidetask ~(p_114_4405)| ~(ismilestone(plan))

...

The additional criteria 'name.up' solved my problem and it looks now like it should to have the desired order.

greetings

alex