feat(dashboards): Avoid issue assignee row fetches#115296
Merged
Merged
Conversation
Issue dashboard tables were fetching the full issue once per assignee cell just to render and update assignment state. Use the row payload for the dashboard assignee cell instead, and keep the post-assignment display update local to that dashboard wrapper. The shared assignment mutation still updates the normal useGroup cache for issue detail consumers. Co-authored-by: Codex GPT-5 <noreply@openai.com>
github-actions
Bot
added
the
Scope: Frontend
Contributor
📊 Type Coverage Diff✅ No new type safety issues introduced. Coverage: 93.47% |
Dashboard issue rows were carrying assignee and link objects directly on TableDataRow, which pushed us toward casts because those rows are meant to stay tabular. Keep the rows scalar and carry issue-only renderer data in table meta instead. Also preserve custom table meta when converting to tabular data so the issue renderers can read it. Co-Authored-By: Codex GPT-5 <noreply@openai.com>
scttcper
changed the title
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 2587d94. Configure here.
shashjar
approved these changes
May 11, 2026
| team: Team; | ||
| }; | ||
|
|
||
| type AssigneeGroup = Pick<Group, 'assignedTo' | 'id' | 'owners'> & { |
Member
There was a problem hiding this comment.
Any reason this is defined twice? Can we export one of them?
The review feedback called out a couple of duplicated local types that could drift. Export the assignee group shape from the dropdown and the issue row metadata shape from the renderer, then reuse those in the nearby consumers. Same behavior, less copy paste. Co-Authored-By: Codex GPT-5 <noreply@openai.com>
nikkikapadia
pushed a commit
that referenced
this pull request
May 12, 2026
Issue dashboard tables were fetching the full issue once per assignee cell just to render and update assignment state. Use the row payload for the dashboard assignee cell instead, and keep the post-assignment display update local to that dashboard wrapper. The shared assignment mutation still updates the normal useGroup cache for issue detail consumers.
3 tasks
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Issue dashboard tables were fetching the full issue once per assignee cell just to render and update assignment state.
Use the row payload for the dashboard assignee cell instead, and keep the post-assignment display update local to that dashboard wrapper. The shared assignment mutation still updates the normal useGroup cache for issue detail consumers.