Sort admin page milestone table by descending due date

[Dirkjan Ochtman <dirkjan@…>]

Currently, the list of milestones in the web admin seems to be sorted by ascending due date. If you have a lot of milestones, that's kind of a pain: the old milestones are likely to be the least interesting. Simply sorting by descending due date probably makes for a better experience (even though it will show far-future milestones before near-future ones).

For a more refined solution, split the table in two parts: a list of open milestones, by ascending due date, and a list of closed milestones, by descending due date.

[Remy Blank]

We could split the table into the same groups as in the ticket form selector: open (by due date), open (no due date) and closed.

[Maynard Koch]

I'll have a look at this one

[Maynard K. <maynard.k@…>]

I did the following:

• simply created three tables
• first shows open milestones with due date
• second shows open milestones without due date
• third shows completed milestones

• every table has its own heading

result:

Any suggestions or comments?

[Maynard K. <maynard.k@…>]

for consistency reasons, one could set the column width the same for all three tables

[Maynard K. <maynard.k@…>]

oh and i reversed sorting order + set utcmin value in sorting function (instead of utcmax) to get properly working descending order for due date

I think the best way would be to sort as Dirkjan suggested:

• ascending or open milestones
• descending for completed milestones

[Jun Omae]

I don't think splitting 1 table to 3 tables is good idea. It is not simple. It brings searching name by my eyes 3 times. Also, currently the table in admin/milestones page has Name, Due, Complete, Default, Retarget, Tickets columns. These columns should be kept.

[figaro]

Would also prefer to maintain the single table.

We could go a long way if:

1. The table is sortable (#11683)
2. A search box is added that allows regular expressions

[Maynard K. <maynard.k@…>]

Replying to Jun Omae:

I don't think splitting 1 table to 3 tables is good idea. It is not simple. It brings searching name by my eyes 3 times. Also, currently the table in admin/milestones page has Name, Due, Complete, Default, Retarget, Tickets columns. These columns should be kept.

These columns are still there; I just cropped the screenshot. But I get your point; it is easier to maintain a single table and makes searching much quicker.

I would try something like what figaro suggested—having a single sortable table with a search box sounds good.

[Maynard K. <maynard.k@…>]

Here is a suggestion for using a single table with an extra search box that allows using regular expressions.

Table is sorted in following order:

• Open milestones (with a due date) → descending by due date
• Open milestones (no due date)
• Closed milestones → descending by due date

(see attachment above, sorry I forgot to fill the description)

[anonymous]

Related #11683, #2130