We have multiple TMS checks. When these are tagged, I would expect the list produced to show me only the checks that match all of the tags I have filtered by ("tag1" AND "tag2"). The observed behaviour is that ANY check matching those tags is listed ("tag1" OR "tag2").
Simple example
Consider 4 TMS checks, with the following tags:
check_1: tag1, tag2
check_2: tag1, tag3
check_3: tag1, tag4
check_4: tag1, tag5
If I filter for tags "tag1, tag3", I would only expect to see a single result "check_2". Instead with the current behaviour, I will see all 4 checks.
Real world example
We have 2 environments: "rapid" and "regular". Each environment has three tiers: "dev", "staging", and "prod". There are 6 transaction checks for each tier. This makes a total of 36 checks.
I have tagged the transaction checks accordingly (e.g. "rapid, dev", "regular, staging" etc.).
I enter the tags "regular" and "dev" into the filter, the behaviour I would expect is to list only the check that match both of these tags ("regular" AND "dev"), giving me 6 results.
However, this actually yields 24 results. This is ALL results tagged "regular" (18 total), and ALL results tagged "dev" (12 total, 6 already discovered from the tag "regular", so 6 additional checks). This is effectively showing a list of all checks tagged "regular" OR "dev".
I believe this behaviour to be counter-intuitive, and it forces us to create compound tag values like "rapid_dev", making tagging and filtering by tags almost useless when we could just use the search.
My request is for an improvement to the logic that applies the tags when displaying results, and to only show transaction checks that match all tags provided, not display transaction checks that match any of the tags provided.
