fix(issue-detection): Use LLM-resolved project_id for cross-project issue attribution#109253
Merged
roggenkemper merged 1 commit intomasterfrom Feb 25, 2026
Merged
Conversation
github-actions
bot
added
the
Scope: Backend
…ssue attribution Distributed traces span multiple projects. When the LLM detects an issue in spans belonging to project B, prefer the issue-level project_id over the request-level one so the issue is attributed to the correct project. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
roggenkemper
force-pushed
the
roggenkemper/fix/cross-project-issue-attribution
branch
from
df8560f to
be166b6
Compare
Member
Author
|
bugbot run |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
shayna-ch
approved these changes
Feb 25, 2026
roggenkemper
deleted the
roggenkemper/fix/cross-project-issue-attribution
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 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.
Distributed traces span multiple projects. When the LLM detects an issue in spans belonging to project B, prefer the issue-level project_id over the request-level one so the issue is attributed to the correct project.