You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a report's content mapping view, you can highlight text which opens a search dialog for the respective highlighted text. However, sometimes, the search query does not correspond to the highlighted text, but some previous search term instead.
Environment
OpenCTI version: 6.4.2
OpenCTI client: frontend
Reproducible Steps
This one is a bit hard to reproduce, unfortunately. From my latest experiences, the best chances to reproduce are by following these steps:
Create a report with some text content (no files needed). For testing purposes, add some keyword such as telecom or South-East Asia (note that these keywords do not correspond to exact entity names).
Go to the report's content mapping view.
Highlight text to open the respective search dialog and map some fields. This should work as intended.
Once you try to map telecom or South-East Asia, you may notice that the respective entities have slightly different names in OpenCTI (Telecommunications and South-Eastern Asia). Sometimes, I won't find the correct entity using the keyword from the report, so I search for the correct name instead. -> Change the search term from South-East Asia to South-Eastern Asia and select the correct result.
Any further mappings won't search for the highlighted terms.
This behaviour does not change with a page refresh and appears, but it seems to be bound to the report entity. In the same OpenCTI session, the content mapping will work again for other reports.
Expected Output
Search dialog in the content mapping view should search for the highlighted text.
Actual Output
Sometimes, it does not.
Additional information
none
Screenshots (optional)
none
The text was updated successfully, but these errors were encountered:
ups1decyber
added
bug
use for describing something not working as expected
needs triage
use to identify issue needing triage from Filigran Product team
labels
Jan 7, 2025
I've struggled a bit to understand the issue. But I think I've been able to reproduce. Can you confirm that you did take the following steps? And that the final problem is the correct one?
Create a report with some text content (no files needed). For testing purposes, add some keyword such as telecom or South-East Asia (note that these keywords do not correspond to exact entity names).
Go to the report's content mapping view.
Highlight text to open the respective search dialog
Change the searched text in the search dialog in the drawer
Close the drawer
Highlight again some text
Result: the search does not search for the highligted search but your previous search.
Description
In a report's content mapping view, you can highlight text which opens a search dialog for the respective highlighted text. However, sometimes, the search query does not correspond to the highlighted text, but some previous search term instead.
Environment
Reproducible Steps
This one is a bit hard to reproduce, unfortunately. From my latest experiences, the best chances to reproduce are by following these steps:
telecom
orSouth-East Asia
(note that these keywords do not correspond to exact entity names).telecom
orSouth-East Asia
, you may notice that the respective entities have slightly different names in OpenCTI (Telecommunications
andSouth-Eastern Asia
). Sometimes, I won't find the correct entity using the keyword from the report, so I search for the correct name instead. -> Change the search term fromSouth-East Asia
toSouth-Eastern Asia
and select the correct result.This behaviour does not change with a page refresh and appears, but it seems to be bound to the report entity. In the same OpenCTI session, the content mapping will work again for other reports.
Expected Output
Search dialog in the content mapping view should search for the highlighted text.
Actual Output
Sometimes, it does not.
Additional information
none
Screenshots (optional)
none
The text was updated successfully, but these errors were encountered: