Sorting a search by priority does not place tickets with milestones above tickets with "none" milestone
In order to sort a large number of tickets, I have created a milestone with no due date. I have called this milestone "Prioritized tickets". When doing a search with sort:priority, tickets in a milestone with a due date are placed above tickets in the prioritized tickets milestone. This is good and what I would expect.
However, tickets with no milestone are mixed with the tickets in the prioritized tickets milestone, with no obvious pattern. All tickets in the prioritized tickets milestone are in the correct order. It just seems odd that tickets with no milestone are placed above some of these tickets.
Is there any workaround to this?
-
lighthousebug.png
75.8 KB
Discussions are closed to public comments.
If you need help with Lighthouse please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Jon on 31 Mar, 2011 08:33 PM
It has now been a week since I posted this, any thoughts?
2 Posted by Nicole on 31 Mar, 2011 08:46 PM
Sorry for the delay. What is your search term? Let us know that and we'll see what's happening.
Thanks,
Nicole
3 Posted by Jon on 31 Mar, 2011 08:49 PM
The screen shot above used the search term "responsible:Jon state:open not-state:qa sort:priority"
4 Posted by Nicole on 01 Apr, 2011 02:48 PM
The results won't group by milestone. Sort by priority is really meant for the context of milestone view, since it's less specific state and more relative placement to other tickets in that milestone. That said, we do have priority states available for accounts on the Bronze plan or higher. That places a specific state on the ticket, so it can be considered in the larger project context. You basically get a choice between priority sorting within a milestone or priority state across the project. When you choose one you lose the other.
Let me know if you have any questions or if I've misunderstood.
Thanks,
Nicole
5 Posted by Jon on 06 Apr, 2011 02:57 PM
This seems counter-intuitive to me. When doing a search and sorting by priority, it seems the milestone is a natural field to group by.
6 Posted by Nicole on 06 Apr, 2011 05:05 PM
I've created a ticket for the behavior we're talking about here. We'll update this discussion when we have more information but at this time it won't group the results by milestone.
Thanks,
Nicole
Nicole closed this discussion on 02 Jul, 2012 08:58 PM.