-
Notifications
You must be signed in to change notification settings - Fork 640
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect tag filter results when observables with tags are added then deleted #1061
Comments
I try to reproduce your problem, but I cant. Could you please describe step 4 more in detail? When I activate filters on the case page, they filter on the tags of the case, not on the tags of the case's observables. Thank you. |
Filtering cases by tag, doesn't rely on observable tags, but only on case tags. So this is expected |
I have some example cases that demonstrate a problem with tag filtering. However, the tags are too identifiable for my business. Happy to share a screenshot/data privately to demonstrate. |
Please if you feel this is a real issue, we will be happy to reopen the issue and fix it. But from what I understood from the issue description, there is a confusion between case tags and observable tags. If you have more details, please share them. |
I misdiagnosed the problem, but believe there is still an issue. Try this: Create a tag on a case called 'test="one two three" Filtering on either tag (and you'll get both cases) |
Can't confirm, at least not for TH 3.4.0-RC1 I added the tag When I'm in the case list and filter for the tag Only if I filter on |
Ok, so this in fact happens in the cases list that rely on the As a workaround, you can use the search page which is more strict. This will be fixed. Note that what breaks things, is the use of |
I just recognized you tagged with I have repeated the above test, with the same result. If I filter for a tag named |
The |
Hi everyone. Does the fix also patches an XSS issue ? |
Problem Description
When an observable is removed from a case, filtering on a tag that belongs/ed to that observable still returns the case in search results.
Steps to Reproduce
You should see only one case, but both are displayed
Possible Solutions
*This would resolve another bug, whereby webhooks are not fired whenever an observables that has previously been deleted is re-added to a case.
Complementary information
The text was updated successfully, but these errors were encountered: