hron
Issues hierarchy sort doesn't work (+ suggestion for fix)
Suppose you have a parent issue, with 4 subtask issues. If you are viewing the page for the parent issue, the Issues Hierarchy table columns appear to be sortable. E.g. it looks like you could sort your subtask issues by a column like Start Date.
However, the sort doesn't actually work. The sort doesn't work because the order is actually determined by the parent.child.each statement in the issues_family_content method in queries_helper_patch.rb. Any sorting applied to the @issues list before that just gets overridden here.
Instead of allowing multiple sortable columns, what about having a fixed position for each subtask? In which each subtask may be moved up or down the list using little green arrows? (Just like the lists of Issue Statuses or Custom Fields in the Redmine Administration area.)
A default position would be assigned on issue creation (position thereby increasing with id), but could be re-ordered as desired. The semantics of the ordering could be interpreted as desired by the user.
If you are interested in this approach, I'm happy to provide the necessary code (in whatever format you please).
Actually, I am use Redmine for a long time now. ;] In general, I think your approach make sense for someone. I ask you only one thing, make this feature optional, add setting for turning this on/off.
