Changes between Version 10 and Version 11 of QueuesPlugin

Timestamp:

Jan 4, 2011, 4:37:30 AM (13 years ago)

Author:

Rob Guttman

Comment:

--

QueuesPlugin

@@ -41 +41 @@
     {{{
     [queues]
-    reports = 9,10
+    reports = 13,14
     }}}
 
@@ -84 +84 @@
 Notice that the first column is the {{{position}}} custom field and is defined as {{{p.value as position}}} - this is ''required''.  The first column's name must always match the name of the custom field used to maintain the queue position.  (You can name them whatever you want; they just have to match.)  In the ORDER BY clause, we cast the position field to an integer.  This example is for sqlite3; you'll need to check the syntax for the database you're using.  If your database does not support casting, you can use position padding option described below.  There are no other restrictions to the SQL you use for your reports (as far as I'm aware!).
 
-If the report above was created as, say, report {{{9}}}, then you would need to add it to the {{{[queues]}}} section of the {{{trac.ini}}} file:
-{{{
-[queues]
-reports = 9
+If the report above was created as, say, report {{{13}}}, then you would need to add it to the {{{[queues]}}} section of the {{{trac.ini}}} file:
+{{{
+[queues]
+reports = 13
 }}}
 
@@ -112 +112 @@
 }}}
 
-If this was created as report {{{10}}}, update the {{{trac.ini}}} file as so (and restart your web server if needed):
-{{{
-[queues]
-reports = 9,10
+If this was created as report {{{14}}}, update the {{{trac.ini}}} file as so (and restart your web server if needed):
+{{{
+[queues]
+reports = 13,14
 }}}
 
@@ -152 +152 @@
 {{{
 [queues]
-reports = 9,10,11
+reports = 13,14,15
 group.triage = clear
 }}}