Advanced Search improvements

[mlodic]

There are some critical improvements to be developed:

• The Frontend GUI loads all the pages at once instead of the first one only and the other ones when requested. That poses several problems while doing some particular researches. It is enough to trigger a single {4,5}xx error and the GUI does not react good (either provides no results or it completely breaks)
• The searched string is not highlighted in the JSON report viewer. That would be a wonderful help for the analyst. Otherwise the analyst is required to look through the available results to find the searched string.

And other minor improvements:

• The datetime picker does not work properly in Firefox, it does show only dates and no chance to change time. The datetime field should be editable manually too.
• The "name" input field could be a more complex component. I would have expected something similar to the Input field used in the "Scan" page to select the analyzers. That would help a lot selecting and finding the correct plugins to search
• The results' table could have integrated filters, similar to the Job History Table. That could help the analysts to do additional pivots inside the obtained results.
• Populate the filter with the url params, like the history sections (if we use the component useDataTable this is done automatically).
• Add the analyzable in the table
• Change text search: support search in every filed not only the report field or change the label to report search with the current behaviour.
• Use also DataModel, no need to index them in elastic, but it could be useful search also inside them

[github-actions]

This issue has been marked as stale because it has had no activity for 10 days. If you are still working on this, please provide some updates.

[suyashgupta2411]

@mlodic Can you please assign this issue to me?

[suyashgupta2411]

@mlodic I have submitted PR for review #2805 for issue #928 . Meanwhile can I work on this? Thank you

[fgibertoni]

@suyashgupta2411 please be patient. You can have only one issue at time assigned, when it's closed you can work on something else

[PradyumnChauhan]

@mlodic @fgibertoni I think this is happening because:
We're making too many API calls upfront instead of as needed,
There's no proper error handling for individual page loads,
The state management doesn't support proper pagination

I'd like to fix this by implementing lazy loading with better error handling. Mind assigning this issue to me? I've been looking to contribute to this area!

[drosetti]

Hi @PradyumnChauhan. Glad that your are interested in this feature! I assign this feature to you, let me know if you have some problems with it

[PradyumnChauhan]

Hi @drosetti . thanks for assigning this feature to me! I'll start working on it right away. I'll be sure to reach out if I run into any issues or need clarification. Looking forward to contributing!

[PradyumnChauhan]

Hi @drosetti @mlodic . Could you clarify which pages this issue appears on? I want to make sure I check the right places. Are there specific sections where the "name" input should behave like the "Scan" page’s analyzer selection field?

[drosetti]

Hi, I added some elements to the checklist. This is a quite huge task, so don't worry about it, if you cannot resolve all of them is fine, every contribution is appreciated!