Audit follow-up: Analytics search pane keeps stale results after query error
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Parent epic: #36004
Finding
The analytics search store reportedly leaves prior results visible after a query error.
Report reference: dotcms-ui/src/app/portlets/dot-analytics/search/dot-analytics-search.store.ts:100-106
Potential impact
Users may interpret stale analytics search results as the current query's results after an error.
Suggested validation
Run a successful analytics search, then force the next query to error and inspect whether stale results remain visible.
Possible fix
Clear or mark results stale on query error while setting an explicit error state.
Caveat
This was AI-found by Claude from .scratch/audit/REPORT.md. Please perform secondary validation of correctness, severity, and value before actioning.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at dotcms-ui/src/app/portlets/dot-analytics/search/dot-analytics-search.store.ts:100-106 and validate the reported behavior by running a successful analytics search, then forcing the next query to error. Done means the prior results are cleared or marked stale and an explicit error state is visible; also confirm the finding's correctness, severity, and value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100