admin wrote:phancox wrote:Is it possible to return to the previous behaviour? Was the change made deliberately for any particular reason?
The previous implementation makes much more sense to me as I see no value in sorting tasks to the bottom of the list purely because they have no sub-tasks.
Yes, this is as-designed, because makes navigation more usable, if you have many leaf-tasks and projects on the same tree level.
Can you move all empty versions to sub-group like "empty versions" ?
OK. I personally like the idea of grouping "folders" above "files", however, in this case they are all "folders"; it just so happens that some of them are empty. The problem is that because of TrackStudio's flexible hierarchy you have no way of differentiating between an "empty folder" and a "file".
You could possibly differentiate based on whether a task permitted sub-tasks. i.e., you would only sort the task to the bottom as per later versions if it could not have sub-tasks otherwise it would retain the previous sort order. This would seem to be the best of both worlds but could possibly be overly complex to code and no doubt won't suit every one.
I'll probably just create a dummy sub-task under my empty tasks. The only reason they're empty is becuase they relate to earlier software releases where we used Bugzilla and didn't migrate all the data into TrackStudio.