Changes between Version 10 and Version 11 of QueuesPlugin


Ignore:
Timestamp:
Jan 4, 2011 5:37:30 AM (4 years ago)
Author:
robguttman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QueuesPlugin

    v10 v11  
    4141    {{{ 
    4242    [queues] 
    43     reports = 9,10 
     43    reports = 13,14 
    4444    }}} 
    4545 
     
    8484Notice 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!). 
    8585 
    86 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: 
    87 {{{ 
    88 [queues] 
    89 reports = 9 
     86If 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: 
     87{{{ 
     88[queues] 
     89reports = 13 
    9090}}} 
    9191 
     
    112112}}} 
    113113 
    114 If this was created as report {{{10}}}, update the {{{trac.ini}}} file as so (and restart your web server if needed): 
    115 {{{ 
    116 [queues] 
    117 reports = 9,10 
     114If this was created as report {{{14}}}, update the {{{trac.ini}}} file as so (and restart your web server if needed): 
     115{{{ 
     116[queues] 
     117reports = 13,14 
    118118}}} 
    119119 
     
    152152{{{ 
    153153[queues] 
    154 reports = 9,10,11 
     154reports = 13,14,15 
    155155group.triage = clear 
    156156}}}