| Reporter |
Lee Prosser (lee.prosser)
|
|---|---|
| Created | Jun 20, 2013 3:36:48 PM |
| Updated | Jun 20, 2013 3:45:53 PM |
| Priority | Normal |
| Type | Usability Problem |
| State | Open |
| Assignee | Vadim Gurov (vgurov) |
| Subsystem | Agile Board |
| Fix versions | Backlog |
| Fixed in builds | No Fixed in build |
| Affected versions | No Affected versions |
| Browser | Any Browser |
| OS | Any OS |
| Verified in build | Not verified |
| Verified by | Nobody |
| Reviewed by | No reviewed by |
| Severity | Routine |
What steps will reproduce the problem?
1. Load up an agile board with lots of issues in differing states/priorities
2. Enter the query "order by:Priority desc"
3. The issues do not display in an ordered fashion
What is the expected result?
I would expect to see the top most issues being of highest priority (in this case show-stopper), then go down each priority until the lowest (in this case minor).
What happens instead?
There seems to be no visible difference in the sorting of the issues
Please provide any additional information below.
In our scenario we have LOTS of issues which are in different swimlanes and are prioritized accordingly, now the developers in this scenario are being told to work on the highest priorities first (so show-stopper), however when a new issue is added it just sits at the bottom of the pile, so you may have 30 show-stoppers in the ready column, however they are not displayed at the top, and manually sorting them all the time is a large time sink due to issues constantly being moved around.
So in this case I would have assumed that you could just tell the board to sort by the priority so the developers will immediately see any important fixes and will then be able to action them working their way down, without any other manual re-arranging.
However it seems like the order by or sort by criteria in the search box is not working.
1. Load up an agile board with lots of issues in differing states/priorities
2. Enter the query "order by:Priority desc"
3. The issues do not display in an ordered fashion
What is the expected result?
I would expect to see the top most issues being of highest priority (in this case show-stopper), then go down each priority until the lowest (in this case minor).
What happens instead?
There seems to be no visible difference in the sorting of the issues
Please provide any additional information below.
In our scenario we have LOTS of issues which are in different swimlanes and are prioritized accordingly, now the developers in this scenario are being told to work on the highest priorities first (so show-stopper), however when a new issue is added it just sits at the bottom of the pile, so you may have 30 show-stoppers in the ready column, however they are not displayed at the top, and manually sorting them all the time is a large time sink due to issues constantly being moved around.
So in this case I would have assumed that you could just tell the board to sort by the priority so the developers will immediately see any important fixes and will then be able to action them working their way down, without any other manual re-arranging.
However it seems like the order by or sort by criteria in the search box is not working.