-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
The validation for the priority field in conditions does not allow the match operation. It will throw the message ""error: matches is not valid operation for priority".
Steps to Reproduce
- Customer has tested this behaviour and lodged a Github page here around it.
- Tested within Terraform with the script:
filter {
type = "match-all-conditions"
conditions { field = "priority" not = false operation = "matches" expected_value = ".*(P1|P2).*" order = 0 }
Expected Results
For the priority to be able to match and properly set when using Terraform.
Actual Results
Example of output:
Workaround
Currently it is possible to set the priority within the integration itself so will need to use that as a workaround rather than via the Go SDK.