Closed (fixed)
Project:
Support Ticketing System
Version:
6.x-1.0
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
22 Jun 2009 at 16:18 UTC
Updated:
23 Jul 2009 at 20:50 UTC
Problem. Everyone selects "order by priority" then someone comes in a second later after an update has been done. They also select "order by priority" but the list order is different. Suggested patch - have secondary sort by # (works for us and everyone is happy).
Add $sql .= ', t.nid DESC ';
to query.
*** 1895,1900 ****
--- 1895,1901 ----
}
$sql = db_rewrite_sql($sql);
$sql .= tablesort_sql($header);
+ $sql .= ', t.nid DESC ';
$sql_count = "SELECT COUNT(DISTINCT(n.nid)) FROM {node} n LEFT JOIN {comments} c ON n.nid = c.nid AND (c.status = %d OR c.status IS NULL) LEFT JOIN {support_ticket} t ON n.nid = t.nid WHERE n.status = 1 AND client = $client $state $my_open";
$sql_count = db_rewrite_sql($sql_count);
$result = pager_query($sql, 50, 0, $sql_count);
Comments
Comment #1
rar commentedUpdated - to most recent version also issue with 1.0.
diff -p support.oldmod support.module
Comment #2
jeremy commentedI agree that this would be useful, however I'm not sure everyone would want the secondary sort column to be the node ID. Feature implemented as a configuration option. In the latest version of the code, visit Administer >> Support ticketing system >> Settings to set a "Secondary sort column".