-
Works at my side. My steps to try:
- Run a brand new OneDev server
- Create a blank project
- Add foud issues with priority respectively
minor,normal,majorandcritical - Open the created project, switch to
issues/boards, and edit the board to specify base query asorder by "Priority". - Now all issues in the board will be sorted as expected.
I guess you are editing the default board in global issue setting directly, and it is different from the board in your project, as you've edited that board already which is no longer the default one.
-
Closing this issue as I was not able to reproduce the issue. It may have been a mistake on my part -- not sure though, there might have been some bug where changing the query order did not take effect when it should have. I will re-open if I can reproduce it again.
-
Previous Value Current Value Open
Closed
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee |
Issue Votes (0)
While the order is correct if entering the same query in "Filter and order issues" in the text box at the top of the board, the default order when that box is empty does not respect the one specified in "Base Query" and "Backlog Base Query" of the board definition.
The order seems to always be "Last Modified" when that box is empty. This is quite inconvenient.
Hmm, after editing the default boards and doing a "Use default boards" the order seems to be correct. I really thought I did "edit' the board directly though.
Perhaps the only way to update the base query after doing "Use default boards" is to do "Use default boards" again?
That is, neither editing the default boards, nor editing the originally default boards directly, works?