Skip to content

fix(seer): Populate missing IssueDetails fields for explorer_index#109213

Merged
shruthilayaj merged 3 commits intomasterfrom
seer/fix/seer-issue-details-fields
Feb 24, 2026
Merged

fix(seer): Populate missing IssueDetails fields for explorer_index#109213
shruthilayaj merged 3 commits intomasterfrom
seer/fix/seer-issue-details-fields

Conversation

@sentry
Copy link
Contributor

@sentry sentry bot commented Feb 24, 2026

This PR addresses a data type mismatch and missing fields in the IssueDetails model when Sentry sends issue data to Seer for explorer indexing.

Previously, the IssueDetails model in getsentry/sentry (src/sentry/seer/sentry_data_models.py) did not include short_id, project, filename, and function fields, which are present in Seer's corresponding IssueDetails model. This led to incomplete data being sent to Seer.

Note: https://github.com/getsentry/seer/blob/main/src/seer/explorer_index/data_indexing.py#L198-L199 checks for project on an issue, so looks like we were just indexing issues because project wasn't being passed via IssueDetail

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Feb 24, 2026
@shruthilayaj shruthilayaj added the Trigger: getsentry tests Once code is reviewed: apply label to PR to trigger getsentry tests label Feb 24, 2026
@shruthilayaj shruthilayaj marked this pull request as ready for review February 24, 2026 19:09
@shruthilayaj shruthilayaj requested a review from a team as a code owner February 24, 2026 19:09
Copy link
Contributor

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Co-authored-by: sentry-warden[bot] <258096371+sentry-warden[bot]@users.noreply.github.com>
@github-actions github-actions bot removed the Trigger: getsentry tests Once code is reviewed: apply label to PR to trigger getsentry tests label Feb 24, 2026
@shruthilayaj shruthilayaj added the Trigger: getsentry tests Once code is reviewed: apply label to PR to trigger getsentry tests label Feb 24, 2026
@shruthilayaj shruthilayaj self-assigned this Feb 24, 2026
…ransaction

Add tests covering the fields added to IssueDetails in the explorer index:
short_id, project, filename, and function from group metadata.

Co-Authored-By: Claude <noreply@anthropic.com>
@github-actions github-actions bot removed the Trigger: getsentry tests Once code is reviewed: apply label to PR to trigger getsentry tests label Feb 24, 2026
@shruthilayaj shruthilayaj added the Trigger: getsentry tests Once code is reviewed: apply label to PR to trigger getsentry tests label Feb 24, 2026
@shruthilayaj shruthilayaj enabled auto-merge (squash) February 24, 2026 19:53
@shruthilayaj shruthilayaj merged commit 3383c5e into master Feb 24, 2026
81 of 85 checks passed
@shruthilayaj shruthilayaj deleted the seer/fix/seer-issue-details-fields branch February 24, 2026 20:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components Trigger: getsentry tests Once code is reviewed: apply label to PR to trigger getsentry tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants