Opened 3 months ago

Last modified 3 months ago

#2509 new enhancement

Reorder /tunnels

Reported by: Reportage Owned by: sadie
Priority: minor Milestone: undecided
Component: apps/console Version: 0.9.40
Keywords: Cc:
Parent Tickets: Sensitive: no

Description

Currently, tunnels created earlier appear at the top of the tables. This should be inverted so that the earlier the tunnels are created (and therefore expiring), the lower down the table they appear, with newly created tunnels appearing at the top of the table.

Additionally, the same sorting algorithm should be applied to Participating tunnels, which are currently unsorted.

Subtickets

Change History (2)

comment:1 Changed 3 months ago by zzz

Part. tunnels are currently sorted by usage (total bandwidth), highest first, which is at least somewhat like oldest-first, same as the other tunnels.

For client tunnels, why is newest-first better than oldest-first? I can't think of a great reason why one is better than the other, really.

comment:2 Changed 3 months ago by Reportage

Looking at the participating tunnels here (just shy of 2.3K), there's not so much correlation between bandwidth usage and creation time.

7 min
24 sec
3 min
25 sec
grace period
41 sec
29 sec
4 min
grace period
3 min
6 min
2 min

For consistency, creation time should be the sorted column.

As for the order, generally newer items tend to feature at the top of tables, with the older/expiring items falling off the bottom of the table. It's more intuitive, in the same way that newest logging entries at the top of the display are easier to read than logs that publish the oldest entries first.

Note: See TracTickets for help on using tickets.