From 89e2b5a5eb46e3fe2c413ac856c2b46713ce5562 Mon Sep 17 00:00:00 2001
From: Malfurious <m@lfurio.us>
Date: Wed, 20 Oct 2021 00:58:52 -0400
Subject: 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>
---
app/class/stage.class.php | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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();
--
cgit v1.2.3