perf(monitors): Batch issue stream detector fetches on Monitors list#116794
Merged
shashjar merged 1 commit intoJun 3, 2026
Merged
Conversation
github-actions
Bot
added
the
Scope: Frontend
shayna-ch
approved these changes
Jun 3, 2026
shashjar
deleted the
shashjar/batch-issue-stream-detector-fetches-on-monitors-list
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves ISWF-2324.
On the Monitors list page, each row individually fetched the project's issue stream detector to compute the connected alerts count. With 20 rows across different projects, this fired up to 20 separate API requests on page load.
This PR introduces an
IssueStreamDetectorContextProviderthat makes a single batch request for all visible projects and distributes results to rows via a React context provider. The logic falls back to the existing per-row hook when the component is used outside the list (e.g. on the detail page).Also,
useIssueStreamDetectorsForProjectis fixed so that the query is skipped whenprojectIdisundefined.