Defect #35794
ProjectQuery doesn't obey multiple sort orders
Status: | New | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | Projects | |||
Target version: | - | |||
Resolution: | Affected version: |
Description
While the new/edit ProjectQuery
form supports setting a secondary and tertiary sort clause, these project custom query settings are not obeyed when rendering the projects index view as a list.
The above is equally true for non-persistent ProjectQuery
sorting. In contrast to IssueQuery
, when sorting by a column is requested (by clicking the column header), the previous sort clause isn't preserved and re-used.
Behavior is observed on Redmine trunk at r21194.
I haven't looked into this and I'm not certain if it's a defect or a not-yet implemented feature.
Related issues
History
#1
Updated by Mischa The Evil over 1 year ago
- Related to Feature #29482: Query system for Projects page added