Changes between Version 35 and Version 36 of QueuesPlugin


Ignore:
Timestamp:
Oct 16, 2016, 8:20:07 AM (7 years ago)
Author:
figaro
Comment:

Further cosmetic changes

Legend:

Unmodified
Added
Removed
Modified
  • QueuesPlugin

    v35 v36  
    11[[PageOutline(2-5,Contents,pullout)]]
    22
    3 = Manages ticket queues via drag-and-drop
     3= Manage ticket queues via drag-and-drop
    44
    55== Description
     
    99The motivation for this plugin is for when you want to organize a work load in the order you intend to tackle it, ie as a work queue. Queues can be defined or segmented by milestone or any field(s) (or no fields). See the [wiki:QueuesPlugin#Examples examples below] for more details.
    1010
    11 == Bugs/Feature Requests ==
     11== Bugs/Feature Requests
    1212
    1313Existing bugs and feature requests for QueuesPlugin are
     
    6666== Examples
    6767
    68 This plugin is built from many parts built into Trac, such as reports and dynamic variables. This approach takes advantage of what Trac already offers natively, while still providing flexibility in how you configure the queues. However, this flexibility is traded off against ease-of-use. So this plugin is for advanced users/administrators only!
     68This plugin is built from many parts of Trac, such as reports and dynamic variables. This approach takes advantage of what Trac already offers natively, while still providing flexibility in how you configure the queues. However, this flexibility is traded off against ease-of-use. So this plugin is for advanced users/administrators only!
    6969
    7070=== Team work queue for all tickets
     
    8585}}}
    8686
    87 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!
     87Notice 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!
    8888
    8989If 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:
     
    163163}}}
    164164
    165 The {{{group.triage = clear}}} tells the plugin that the {{{Triage}}} group shouldn't reorder positions (reordering is the default operation).  The group name {{{Triage}}} is just an example - you can use any name as long as you make the config match it. Here's the screenshot of the report:
     165The {{{group.triage = clear}}} tells the plugin that the {{{Triage}}} group shouldn't reorder positions (reordering is the default operation). The group name {{{Triage}}} is just an example - you can use any name as long as you make the config match it. Here's the screenshot of the report:
    166166
    167167[[Image(example3.png, border=2)]]