keephq
[🐛 Bug]: always generating incidents report for all even provided specific time range / specific selected incidents
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
- Go to '...' incidents page
- Click on '....' generate report
- Scroll down to '....'
- See error --- Giving all incidents repost insted of givung specific time and specific incidents
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.
The incident report generation currently includes all incidents unless you set a time range filter or other filters in the UI. The backend supports filtering by time range and specific incidents using CEL queries and allowed incident IDs, but the frontend only passes the table filters (like time range) to the report—not the manually selected incidents. If you want the report to cover a specific time window, use the date range picker before generating the report. Filtering by only selected incidents is not supported in the report feature right now; this is a UX/design gap rather than a backend bug. More details on filtering logic are in the code and docs: source, source, source.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
![dosubot[bot] avatar](https://avatars.githubusercontent.com/in/324583?v=4 "Published by a pub.dev verified publisher"){kind=small}
I've checked the code and current behavior: incident reports are generated based on the filters you set in the UI (like time range, severity, status, etc.), but not on manually selected incidents. The report uses the CEL filter string from the table view, so if you filter to a specific time window or facet, the report should match that filter. However, selecting incidents with checkboxes does not affect the report output—this is a limitation in the frontend design, not a backend bug. If you want the report to only include certain incidents, use the filters and date range picker before generating the report. Filtering by manual selection is not supported right now.
You can see this logic in the code for the report modal and filtering:
Let me know if you want more details or have questions about possible workarounds!
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@dosu
pls check again i have given past day there 2 incidents but giving all incidents report
The report should only include incidents matching your current filters (like "past day"), but the code shows this depends on the CEL filter string (filterCel) being correctly updated and passed to the report modal when you click "Generate report" — the backend always respects this filter if set, so if you see all incidents in the report, it's almost certainly a frontend issue with the filter state or timing source source source.
Manual selection (checkboxes) does not affect the report; only the table filters do. If the modal opens before the filter updates, or filterCel is stale/empty, the backend will return all incidents. You can debug this by inspecting/logging the filterCel value right before opening the report modal to confirm it matches your intended filters.
If you need help checking the filterCel value or want to troubleshoot further, let me know!
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
The report is including all incidents because of a frontend timing issue: after you change filters (like time range or facets), the CEL filter string that controls what gets reported is updated with a short delay (debounced by ~100ms). If you click "Generate report" immediately after changing filters, the report modal may receive an old or empty filter, so the backend returns all incidents instead of just the filtered set. This is a known frontend race condition and matches similar bugs reported with facet filters and CEL state management (source, source, source).
To work around this, wait a second or two after changing filters before clicking "Generate report" to ensure the filter state updates. You can also check the Network tab in DevTools: the CEL filter sent with the report request should match the one used for the incidents table. If the issue persists, try reapplying filters or refreshing the page. Avoid using presets for multi-value filters, as they can also cause filter merging bugs.
If you want to debug further, log or inspect the CEL filter value right before opening the report modal to confirm it matches your intended filters. Let me know if you want help with code-level debugging or more details on the filter state logic.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other