Changes between Version 33 and Version 34 of QueuesPlugin


Ignore:
Timestamp:
Nov 19, 2015, 8:57:11 AM (8 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified
  • QueuesPlugin

    v33 v34  
    1515
    1616If you have any issues, create a
    17 [http://trac-hacks.org/newticket?component=QueuesPlugin&owner=robguttman new ticket].
     17[/newticket?component=QueuesPlugin new ticket].
    1818
    1919[[TicketQuery(component=QueuesPlugin&group=type,format=progress)]]
     
    2121== Download
    2222
    23 Download the zipped source from [download:queuesplugin here].
     23Download the zipped source from [export:queuesplugin here].
    2424
    2525== Source
    2626
    27 You can check out QueuesPlugin from [http://trac-hacks.org/svn/queuesplugin here] using Subversion, or [source:queuesplugin browse the source] with Trac.
     27You can check out QueuesPlugin from [/svn/queuesplugin here] using Subversion, or [source:queuesplugin browse the source] with Trac.
    2828
    2929== Configuration
     
    3636}}}
    3737
    38  See [http://trac.edgewall.org/wiki/TracPlugins TracPlugins] for more installation details and options. You will likely need to restart Trac's web server after installation.
     38 See [t:TracPlugins] for more installation details and options. You will likely need to restart Trac's web server after installation.
    3939
    4040 2. Enable the plugin by adding the following to your `trac.ini` file:
     
    5656  * Can use spaces, which will get removed.
    5757
    58  5. Tell the queues plugin which reports to convert to queues, example `trac.ini` file:
     58 5. Tell the plugin which reports to convert to queues, example `trac.ini` file:
    5959 {{{#!ini
    6060[queues]
     
    7777FROM ticket t
    7878LEFT JOIN enum s ON s.name = t.severity AND s.type = 'severity'
    79 LEFT OUTER JOIN ticket_custom p ON p.ticket = t.id and p.name = 'position'
     79LEFT OUTER JOIN ticket_custom p ON p.ticket = t.id AND p.name = 'position'
    8080WHERE t.status <> 'closed'
    8181ORDER BY CAST((CASE p.value
     
    9393}}}
    9494
    95 You may need to restart your Trac web server afterwards. Here's a screenshot of the result with a few sample tickets:
     95You may need to restart your Trac web server afterwards. Here is a screenshot of the result with a few sample tickets:
    9696
    9797[[Image(example1.png)]]
     
    108108FROM ticket t
    109109LEFT JOIN enum s ON s.name = t.severity AND s.type = 'severity'
    110 LEFT OUTER JOIN ticket_custom p ON p.ticket = t.id and p.name = 'position'
    111 WHERE t.status <> 'closed' and t.milestone = '$MILESTONE'
     110LEFT OUTER JOIN ticket_custom p ON p.ticket = t.id AND p.name = 'position'
     111WHERE t.status <> 'closed' AND t.milestone = '$MILESTONE'
    112112ORDER BY CAST((CASE p.value
    113113                 WHEN '' THEN '0'
     
    128128[[Image(example2.png)]]
    129129
    130 In this example, I'm using the optional DynamicVariablesPlugin which converts the {{{MILESTONE}}} dynamic variable (aka argument) from a freeform textbox to a convenient dropdown menu at the right.
     130In this example, the optional DynamicVariablesPlugin is used, which converts the {{{MILESTONE}}} dynamic variable (aka argument) from a freeform textbox to a convenient dropdown menu at the right.
    131131
    132132=== Team work queue per milestone with a Triage group
     
    140140             ELSE '$MILESTONE'
    141141            END) AS __group__,
    142        p.value as position, t.id AS ticket, summary,
     142       p.value AS position, t.id AS ticket, summary,
    143143       t.type AS type, t.severity, t.owner
    144144FROM ticket t
    145145LEFT JOIN enum s ON s.name = t.severity AND s.type = 'severity'
    146 LEFT OUTER JOIN ticket_custom p ON p.ticket = t.id and p.name = 'position'
    147 WHERE t.status <> 'closed' and t.milestone = '$MILESTONE'
     146LEFT OUTER JOIN ticket_custom p ON p.ticket = t.id AND p.name = 'position'
     147WHERE t.status <> 'closed' AND t.milestone = '$MILESTONE'
    148148ORDER BY (CASE p.value
    149149                 WHEN '' THEN 'Triage'
     
    175175 * {{{ignore}}}
    176176
    177 There must be only one {{{reorder}}} group per report but you can have any number of {{{clear}}} and {{{ignore}}} groups. The {{{ignore}}} operation will simply list the tickets that match your grouping but tickets can't be moved out of or into it. This is useful, for example, if you want to show work in the queue that has been implemented but still in, say, a {{{verifying}}} state and not yet closed. The SQL syntax is left as an exercise to the reader.
    178 
    179 TIP: You can click on any {{{clear}}} or {{{ignore}}} group heading to toggle between hiding and showing its tickets.
     177There must be only one {{{reorder}}} group per report but you can have any number of {{{clear}}} and {{{ignore}}} groups. The {{{ignore}}} operation will simply list the tickets that match your grouping, but tickets can't be moved out of or into it. This is useful, for example, if you want to show work in the queue that has been implemented but still in, say, a {{{verifying}}} state and not yet closed. The SQL syntax is left as an exercise to the reader.
     178
     179'''Tip''': You can click on any {{{clear}}} or {{{ignore}}} group heading to toggle between hiding and showing its tickets.
    180180
    181181=== Team work queue per custom field
     
    193193=== Personal work queue
    194194
    195 You can create a queue for just about any SQL report as long as the {{{position}}} custom field is used for one and only one queue. Another use case is if you want to use queues simply to let users manage their own work load. You can simply create a report that pivots on the special, built-in {{{$USER}}} dynamic variable. Viola! Personal work queues for everyone using a single report.
     195You can create a queue for any SQL report as long as the {{{position}}} custom field is used for one and only one queue. Another use case is if you want to use queues simply to let users manage their own work load. You can simply create a report that pivots on the special, built-in {{{$USER}}} dynamic variable. Viola! Personal work queues for everyone using a single report.
    196196
    197197=== Team work queue ''and'' personal work queue
     
    248248Depending on how you use work queues, several complementary plugins may enhance the user experience:
    249249
    250  * DynamicVariablesPlugin - as described above, this converts dynamic variable textboxes into dropdown menus for those fields which are select fields.  This can make navigating amongst queues much easier.
    251  * DynamicFieldsPlugin - allows you to clear the {{{position}}} field when the milestone/queue field changes and hide the {{{myposition}}} field from general view.  These are just small examples of how the plugin can enhance the user experience of this queues plugin.
    252  * HideChangesPlugin - can hide ticket changes that do not have comments thus reducing the noise from queue reordering changes.  See the next audit section for other options.
    253  * QuietPlugin - dynamically disables email sending when using the AnnouncerPlugin which helps reduce low-value email noise when using the {{{ticket}}} audit option, see below.
     250 * DynamicVariablesPlugin - as described above, this converts dynamic variable textboxes into dropdown menus for those fields which are select fields. This can make navigating amongst queues much easier.
     251 * DynamicFieldsPlugin - allows you to clear the {{{position}}} field when the milestone/queue field changes and hide the {{{myposition}}} field from general view. These are just small examples of how the plugin can enhance the user experience of this queues plugin.
     252 * HideChangesPlugin - can hide ticket changes that do not have comments thus reducing the noise from queue reordering changes. See the next audit section for other options.
     253 * QuietPlugin - dynamically disables email sending when using the AnnouncerPlugin, which helps reduce low-value email noise when using the {{{ticket}}} audit option, see below.
    254254
    255255=== Auditing ticket reorderings