9 | | The motivation for this plugin is for when you want to organize a queue of tickets in the order you intend to tackle the work. Tickets could either use the milestone field as the 'bucket' or use a separate (custom) field. An example may be helpful. |
| 9 | The motivation for this plugin is for when you want to organize a queue of tickets in the order you intend to tackle the work. 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. |
| 10 | |
| 11 | |
| 12 | == Configuration == |
| 13 | 1. Install the plugin (after downloading and unzipping): |
| 14 | {{{ |
| 15 | cd queuesplugin/0.12 |
| 16 | sudo python setup.py bdist_egg |
| 17 | sudo cp dist/TracQueues*.egg /your/trac/location/plugins/ |
| 18 | }}} |
| 19 | |
| 20 | See [http://trac.edgewall.org/wiki/TracPlugins TracPlugins] for more installation details and options. You'll likely need to restart Trac's web server after installation. |
| 21 | |
| 22 | 2. Enable the plugin: |
| 23 | {{{ |
| 24 | [components] |
| 25 | queues.* = enabled |
| 26 | }}} |
| 27 | |
| 28 | You can alternatively use the Trac Web Admin GUI to enable any or all rules. |
| 29 | |
| 30 | 3. Create a custom field to contain the position information - example {{{trac.ini}}} config: |
| 31 | {{{ |
| 32 | [ticket-custom] |
| 33 | position = text |
| 34 | }}} |
| 35 | |
| 36 | 4. Create/modify reports to be used as ticket queues whose first column's name must match the (custom) field created in step 3 above: |
| 37 | * Can contain uppercase characters (which will get converted to lowercase) |
| 38 | * Can use spaces (which will get removed) |
| 39 | |
| 40 | 5. Tell the queues plugin which reports to convert to queues - example {{{trac.ini}}} config: |
| 41 | {{{ |
| 42 | [queues] |
| 43 | reports = 9, 10 |
| 44 | }}} |
| 45 | |
| 46 | See the [wiki:QueuesPlugin#Examples examples below] for more detailed configuration examples and capabilities. |
| 47 | |