[Patch] request ability to use multiple fields in a triage

[anonymous]

it would be extremely nice to be able to use an arbitrary number of fields in a triage. If this is already possible, then it would be extremely nice if it were documented.

[anonymous]

This patch was my solution to this issue; it allows you to specify the triage_field as "complex_triage" to unlock the ability to use multiple fields with some logic (and and or, but no not and no parentheses), as well as one macro value that I had need of (<<component_owner>>). This could probably benefit from further work (like maybe some hook to allow more macros to be defined without having to edit the source, as well as the capability to parse more difficult logic).

It takes advantage of the fact that the first successful transition is the one that gets used so that you can overload a given triage element by starting with the most specific and working your way to the least.

[anonymous]

I forgot to mention: this does not break backwards compatibility with existing triage setups; it only activates if you use complex_triage for the field. If you do that, then you need to re-setup your triage transitions. The new format is field:value for testing the value within the given field against the given value. These can be separated by & (for and) and | (for or) to make up a test. If the test evaluates to try, then the triage goes to the given state. tranisition: <logical block>-><new state> logical block: <test>[op][test]... test: <field>:<value> op: & or | new state: any valid state in your workflow - this is the state to go to, if the logical block evaluates to true.

[anonymous]

just adding patch to the title since there is a patch provided.

[Eli Carter]

While interesting, something about putting that much logic into the triage functionality feels... wrong. I'll leave this ticket open so others can use the patch, but I'm not planning on incorporating it into the plugin.