feat(seer): add seerSuggested assignment source to frontend - #120528
Conversation
Additive changes to assignment source types and lookup objects so the UI can render Seer-suggested assignments. Backend wiring lands separately. Co-authored-by: Cursor <cursoragent@cursor.com>
github-actions
Bot
added
the
Scope: Frontend
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
saponifi3d
left a comment
saponifi3d
left a comment
There was a problem hiding this comment.
lgtm - might be worth taking a look at what the bot said about the rendered text.
Story previewsPreview the stories changed in this PR on the Vercel deployment: Preview deployment: https://sentry-6lpt5gvve.sentry.dev |
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 74839e3. Configure here.
| }), | ||
| ownershipRule: t('Matching Issue Owners Rule'), | ||
| projectOwnership: t('Matching Issue Owners Rule'), | ||
| seerSuggested: t('Seer Suggestion'), |
There was a problem hiding this comment.
Awkward Seer suggestion tooltip text
Low Severity
suggestedReasons uses the short label Seer Suggestion in the descriptive tooltip slot. That text sits under the existing Suggestion: heading, so the UI reads as redundant (Suggestion: … / Seer Suggestion). Nearby reasons use explanatory phrases instead, and getAssignmentSourceLabel has the same short label in the assigned-source tooltip.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 74839e3. Configure here.
2 participants
Additive changes to assignment source types and lookup objects so the UI can render Seer-suggested assignments.
FE split of #119945