98 | | In this example, report 2 uses both {{{queue}}} and {{{milestone}}} fields to define a queue whereas report 9 uses only the {{{queue}}} field. |
| 98 | In this example, report 2 uses both {{{queue}}} and {{{milestone}}} fields to define a queue whereas report 9 uses only the {{{queue}}} field. You may also specify additional filters to skip tickets with certain field values: |
| 99 | {{{ |
| 100 | [analyze] |
| 101 | queue_fields.9 = queue,type!=epic,phase!=verifying|releasing |
| 102 | }}} |
| 103 | |
| 104 | In this example, the {{{queue}}} field defines the queue in report 2 and any ticket in this queue with {{{type}}} equal to "epic" or {{{phase}}} equal to "verifying" or "releasing" will be skipped. (These would typically match the {{{WHERE}}} clause in the report's SQL.) |