-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
3
-
Not defined
Context:
With OPT-4004, the genric filter operators' string fields were replaced by a dedicated filter operator enum class. However, each filter operator support different operators and should, thus, have different enums to indicate which operators are allowed for that field. For example, the variable filter operator field allows all possible operators (such as >, <, >=, etc.), whereas the duration filter operator field only supports is and is not.
AT:
- there are dedicated enum classes for every filter operator field
This is the controller panel for Smart Panels app
- is duplicated by
-
OPT-3793 Introduce an enum for filter operators
- Done
- links to
1.
|
Create dedicated filter operateror enum for IndentityLinkFilter | Done | Unassigned | |
2.
|
Create dedicated filter operateror enum for DurationFilterDataDto | Done | Unassigned | |
3.
|
Create dedicated filter operateror enum for OperatorMultipleValuesFilterDataDto | Open | Unassigned | |
4.
|
Create dedicated filter operateror enum for DoubleVariableFilterDataDto | Open | Unassigned | |
5.
|
Create dedicated filter operateror enum for LongVariableFilterDataDto | Open | Unassigned | |
6.
|
Create dedicated filter operateror enum for ShortVariableFilterDataDto | Open | Unassigned | |
7.
|
Create dedicated filter operateror enum for StringVariableFilterDataDto | Open | Andromachi Rozaki | |
8.
|
Create dedicated filter operateror enum for ExecutedFlowNodeFilterDataDto | Done | Unassigned |