-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
3
-
S
Context:
See comment in PR description: https://github.com/camunda/camunda-optimize/pull/3732#issue-695066628
Now that we have quite a few Flownode viewLevel filters that need instance matching, we should adjust the instance and flownode filter methods in ModelElementFilterQueryUtil to ideally have a very similar structure so it's easier to read. Also, adjust `add..Filter` methods to not "double nest" the filters (see explanation in PR) if possible (though we should make sure to double check if this kind of nesting has a reason).
AT:
- ModelElementFilterQueryUtil is easier to read, especially addInstanceFilterForRelevantViewLevelFilters
This is the controller panel for Smart Panels app
[OPT-5442] Adjust ModelElementFilterQueryUtil instanceMatching and to not double nest filters
Rank | New: Ranked lower |
Labels | Original: current_release refactoring | New: refactoring |
Labels | Original: refactoring | New: nice_to_have potential_for_next_quarter refactoring |
Effort | Original: Not defined [ 11259 ] | New: S [ 11254 ] |
Status | Original: Open [ 1 ] | New: Scheduled [ 10912 ] |
PM Priority | New: 3 |
Labels | Original: nice_to_have potential_for_next_quarter refactoring | New: maintenance nice_to_have potential_for_next_quarter refactoring |
Status | Original: Scheduled [ 10912 ] | New: Open [ 1 ] |
Assignee | Original: Helene Waechtler [ helene.waechtler ] |