Reports Search page: DateTime inputs overflow causing UI layout issues

[srijan2607]

What happened

On the Reports Search page (/search), the "End time" and "Errors" form fields are overlapping/overflowing horizontally. The datetime-local input fields are too wide for their container columns, causing them to extend beyond their boundaries and overlap with adjacent form elements.

Environment

1. OS: macOS (also reproducible on other platforms)
2. IntelOwl version: Latest develop branch (commit 2ef233e)

What did you expect to happen

The form fields in the Reports Search page should be properly contained within their respective columns without any overflow or overlapping. All datetime inputs should have consistent styling and fit within the responsive grid layout.

How to reproduce your issue

1. Navigate to the IntelOwl web interface
2. Go to Reports → Search (or directly to /search)
3. Observe the second row of form fields containing "Start time", "End time", and "Errors"
4. Notice that the "End time" datetime inputs overflow into the "Errors" column area

Error messages and logs

No JavaScript errors in console. This is a CSS/layout issue only.

Screenshots

Suggested Fix

• Add maxWidth constraint to datetime-local inputs
• Add overflow-hidden to the containing columns
• Add flex-wrap to the row for better responsive behavior

[srijan2607]

@fgibertoni can you assign this to me ??

[fgibertoni]

Hey @srijan2607, you already have an open issue assigned.
To enable anyone to contribute we assign one issue per person until that issue is closed.

[NobleCoder69]

Hi! I would like to work on this issue.
Could you please assign it to me?

[IshaanXCoder]

Heyy @fgibertoni , I would like to work on this isssue, could you assign this to me?

[fgibertoni]

Hey @IshaanXCoder, are you still interested in working on this?

[IshaanXCoder]

yeah i'll definitely work on this, pls assign this to me @fgibertoni

[IshaanXCoder]

@fgibertoni could you please share a way to contact you? I’m facing some issues setting up the project locally.

[srijan2607]

@fgibertoni the assigned PR has already been completed and since I have already put it up as a pull request, it will make sense to merge it. Can you please take a look?

#3097

[fgibertoni]

@IshaanXCoder you can reach out to us on Slack

@srijan2607 please be patient. the issue was not assigned to you and another person asked before you to work on it.

[IshaanXCoder]

@fgibertoni pls check your slack dm