Ticket #456: Ticket Order

Please keep tickets that are the next release first. Ordering should be first by milestone: The mile stone order should be something like: 4.0.0RC2, 4.0.0, 4.1.0, 5.0.0, 4.0.0RC1.

That is first the next release, then the previous 4.0.0 (no RC), then 4.1.0 (future), then 5.0.0 (much further into the future), 4.0.0RC1 (past).

The way things are now, you will have this ticket at the top of the list. I don't think this makes sense. Even if it is 'blocking'.

I am really tired of seeing sets.e on the top of the list when we aren't supposed to be committing anything related to it.


Type: Feature Request Severity: Minor Category: General
Assigned To: unknown Status: Is Valid? Reported Release: 4333
Fixed in SVN #: View VCS: none Milestone:

1. Comment by jeremy Nov 28, 2010

I'm not sure if this is the best order. The order right now is based on Severity. sets.e was improperly statused as "Blocking"

It's not blocking anyone's progress with their application. wiki:AboutTickets should be consulted for a clear understanding of what severity and status are.

If we order by milestone then we will tend to see only items that have already been assigned a milestone and not new, severe bugs. If you want to see just milestone, X.X.X, you can choose the filter and bookmark it.

Somewhere in the future of our ticket system there is the idea of user sorting as well as "My Queries" that would save queries that you perform often, i.e. 4.0.0RC2 for example.

Marking Is Valid? for other peoples comments.

2. Comment by jeremy Nov 28, 2010

Maybe we should order by Severity, then Status = New, then Milestone. That way new tickets and severe tickets appear first, then by milestone. I'll think about this more.

3. Comment by jeremy Nov 28, 2010

Moved to a minor status as there are easy ways to work around this issue. BTW... Blocking means the person cannot work around the issue presented, their project is "Blocked" until the bug is fixed.

4. Comment by SDPringle Nov 29, 2010

To me, it is useful to see what needs to be done 'next,' first in order of what is more immediate.

5. Comment by jeremy Nov 29, 2010

Which is the blocking and major bugs, right?

6. Comment by jeremy Dec 02, 2010

See: hg:euweb/rev/1585c8b1c062

Default sort order is now severity, then tickets assigned to a milestone, then tickets not assigned to a milestone. Thus, Blocking 4.0RC1, Blocking 4.1, Blocking (unassigned), Normal 4.0RC1, Normal (unassigned), Minor 4.1, Minor (unassigned), ... Work on ticket 456


Quick Links

User menu

Not signed in.

Misc Menu