Secondary sorting after sorting by parent task
Added by Jānis Elmeris over 11 years ago.
Updated over 1 year ago.
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.
I am seeing the same problem. Sort of curious what is going on with this one as it is fairly critical for my implementation.
We have the same issue. It's problematic as I want to sort issues by priorities, but still have the subtasks grouped under their parent.
Parent, Priority just ignores the latter.
+1. This is indeed very essential to be in Redmine.
+1 I have this problem too
Any news on this?
redmine_smart_issues_sort wouldn't run on 2.3, saying:
undefined method 'issues' for class 'Query'
on line 12 lib/query_patch.rb
Any clues are most appreciated.
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.
- Has duplicate Defect #20123: Can't sort by multiple fields when sorting by parent added
+1 causing us a problem and the patch doesn't seem compatible with v 3.1
I'm getting more and more complains about this. We have thousands of issues per project organized in a tree structure and this defect is very, very painful.
+1, having the same issue, same use case. I would think this should be a simple fix... but I haven't looked at the code
plugins and patches no longer work
- Has duplicate Defect #31840: Sort by Parent does not work as expected added
Confirmed here as well; when 1st ordering is for parent issue, ties (i.e. no parent or same parent) are not resolved using any following filter which makes tree-like views practically impossible.
- Has duplicate Defect #34818: Do not display in the order set in the custom query! added
This is problematic, the secondary sort would be really useful, while still maintaining the parent structure.
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.
Also available in: Atom