I tried creating a device group called Non-Chillers to setup rules. It would be nice to have a != operator.
Its more intuitive to select the type first, then the conditions after that.
Using this approach, operators could be customized better. E.g.: For strings, we could show - equals, contains, starts with, ends with, not contains etc.
Steps to reproduce
[First step]
[Second step]
[and so on...]
Expected behavior
...
Current behavior <!-- The actual behavior observed --
Type of issue
Description
I tried creating a device group called Non-Chillers to setup rules. It would be nice to have a != operator. Its more intuitive to select the type first, then the conditions after that. Using this approach, operators could be customized better. E.g.: For strings, we could show - equals, contains, starts with, ends with, not contains etc.
Steps to reproduce
Expected behavior
...
Current behavior <!-- The actual behavior observed --
...
Known workarounds
...
Possible solution
...
Context and Environment
Screenshot