Changes between Version 4 and Version 5 of QueuesPlugin


Ignore:
Timestamp:
Jan 4, 2011, 4:54:38 AM (4 years ago)
Author:
robguttman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QueuesPlugin

    v4 v5  
    77This plugin converts one or more reports into ticket 'queues'.  A ticket queue allows you to drag-and-drop tickets into your desired order (similar to the Netflix Queue).  Ticket positions in a queue get maintained in a custom field of your choosing.
    88
    9 The motivation for this plugin is for when you want to organize a work load in the order you intend to tackle it - i.e., as a work queue.  Tickets could either use the milestone field as the 'bucket' or use a separate (custom) field.  See the [wiki:QueuesPlugin#Examples examples below] for more details.
     9The motivation for this plugin is for when you want to organize a work load in the order you intend to tackle it - i.e., as a work queue.  Queues can be defined by milestone or any field(s).  See the [wiki:QueuesPlugin#Examples examples below] for more details.
    1010
    1111
     
    4141    {{{
    4242    [queues]
    43     reports = 9, 10
    44     }}}
    45 
    46 See the [wiki:QueuesPlugin#Examples examples below] for more detailed configuration examples and capabilities.
     43    reports = 9,10
     44    }}}
     45
     46See the [wiki:QueuesPlugin#Examples examples below] for more detailed configuration examples, options and capabilities.
    4747
    4848
     
    6464
    6565== Examples ==
    66 This plugin is built from several simple parts many of which are built into Trac (e.g., reports, dynamic variables).  This is to take advantage of what Trac already offers while still providing a great deal of flexibility in how you configure the queues.  Which means you can shoot yourself in the foot if not careful.
     66This plugin is built from several simple parts many of which are built into Trac (e.g., reports, dynamic variables).  This approach takes advantage of what Trac already offers while still providing a great deal of flexibility in how you configure the queues.  However, this flexibility is traded off against ease-of-use.  So consider this a warning that this plugin is for advanced users/administrators only!
    6767
    6868=== Team work queue for all tickets ===
     
    8282}}}
    8383
    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 must always match the name of the custom field used to maintain the queue position.  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!).
     84Notice 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
    8686If 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: