diff options
author | Malfurious <m@lfurio.us> | 2021-10-20 00:58:52 -0400 |
---|---|---|
committer | Malfurious <m@lfurio.us> | 2021-10-20 00:58:52 -0400 |
commit | 89e2b5a5eb46e3fe2c413ac856c2b46713ce5562 (patch) | |
tree | 2c87ae08855f730b2044a3012004b15ef2c5f8e4 /app | |
parent | 8c7803c153edf0d06fa37053faa2e093ded00b4f (diff) | |
download | scrott-89e2b5a5eb46e3fe2c413ac856c2b46713ce5562.tar.gz scrott-89e2b5a5eb46e3fe2c413ac856c2b46713ce5562.zip |
Order most recent issues first
Issue ordering within pad stages is updated to be first by due date
(this was already the case), then by issue number _in decending order_.
This is to be more consistent with the 'closed issues' view for pads,
which always lists the most recently closed issues first. Furthermore,
I suspect users will more likely want to deal with recent issues when
browsing a pad.
Signed-off-by: Malfurious <m@lfurio.us>
Diffstat (limited to 'app')
-rw-r--r-- | app/class/stage.class.php | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/app/class/stage.class.php b/app/class/stage.class.php index 43bb3c3..5d24465 100644 --- a/app/class/stage.class.php +++ b/app/class/stage.class.php @@ -105,7 +105,7 @@ class stage extends obj { $query = "SELECT o.guid FROM objects o JOIN issues i ON o.guid = i.guid " . "WHERE o.objtype = 'issue' AND o.parent = '" . database::esc($this->guid) . - "' ORDER BY i.due, i.numb"; + "' ORDER BY i.due, i.numb DESC"; $res = database::query($query); $issues = array(); |