Secondary sorting after sorting by parent task
I've created a custom query with two sort orders: 1) Parent task - Ascending (as I want my subtasks be grouped visually together), 2) Updated - Descending (as I want to see the most recently changed tasks at the top).What I would expect is that
- all the tasks without parents would be sorted by their "Updated" value;
- all the subtasks within the same parent task would be sorted by their "Updated" value.
As can be seen in the attached screenshot, the actual result in the example of "http://www.redmine.org/projects/redmine/issues" is all the non-parent tasks sorted by their IDs.
All the versions to be submitted along with a bug reports, please take from the current http://www.redmine.org installation, where I'm submitting the defect in. The test screenshot is taken from here.
#2 Updated by Vitaly Klimov about 10 years ago
Please check my plugin - it solves this behavior:
#10 Updated by Nicolas Ph over 8 years ago
Well, i have the same issue, a custom query with "Parent task" as first sort field, the second field is ignored, whatever it is. The result look like the second field is set to 'Created'.
The same issue exists when sorting issue by clicking on columns : After adding the 'Parent Task' to the issue view, I click on "Updated" for example, and then on 'Parent Task', the previous 'Updated' order is completely lost.
By the way, the gantt view with the same query seems to work right.
In case it is useful for anyone else.
After waiting for this to be implemented I finally made my own solution.
You can find it here:
It is an small development that creates an extra index that you can use to get hierarchical tree and allows use aditional sorting criterias for deep issues in tree.
It helps me to get human reports sorting issue tree as I want.