Filtering sessions by minimum number of actions when "contains-command" filter is also applied #1
Description
When we provide a command to filter sessions in the search, the "number of actions counted" (the other possible filter) is applied over the statements which contain the command and not over all the statements of that session.
See the conflicting query here.
For example, imagine we have the session "A" where the user typed "ping" 3 times among other 30 actions. If containsCmd is "ping" and minStatements is 2, the query will return session A. However, if we search for sessions with more than 20 actions (minStatements == 20) where "ping" was typed, session A will not appear.
This is a bug since the minStatements is intended to be applied over all the statements in a session and not only over those ones that match the rest of filters.