-
Spike
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
None
-
None
-
False
-
-
False
-
None
-
None
-
NetObserv - Sprint 272, NetObserv - Sprint 273, NetObserv - Sprint 274, NetObserv - Sprint 275
Follow-up on NETOBSERV-1025, cf comment from Julien here: https://github.com/netobserv/network-observability-console-plugin/pull/343#issuecomment-1625376991
With the new "back and forth" option to show return traffic, the chips layout should be revisited:
- In "match any" mode, by removing the mention of "source" and "destination", and they overlap
- In "match all" mode, we should somehow represent two "super-groups" of chips (each can be composed of the usual groups such as "Namespace", "Node" etc.) and a bidirectional arrow between them to make it more visible that we're querying back and forth traffic between these two groups.
- relates to
-
NETOBSERV-2182 Issues with One way / Back and forth option
-
- Code Review
-
-
NETOBSERV-2183 PoC : Provide a way to change the filter field
-
- Code Review
-
- links to