Repository navigation
fix(discord-bot): stop treating Sentry short ids as Jira keys - #415
Merged
Merged
Conversation
Sentry short ids (SCANNER-313) match the Jira PROJ-123 shape, so the thread-info pin labelled sentry.io issues as Jira and injected jira: SCANNER-313 into agent turns. Skip sentry.io URLs, Sentry-bot authors, and Sentry embeds when extracting Jira keys; drop already-stored false positives on pin refresh/backfill; persist sentry issue URLs and render them under Sentry on the pin.
Label Sentry Discord embeds with the footer short id (SCANNER-313) instead of the numeric issue path, pin them under **Sentry**, and re-inject the URLs as `sentry:` on later turns so they are not treated as Jira keys.
patroza
marked this pull request as ready for review
August 20, 2026 08:51
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
1 participant
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.
Why
Sentry short ids (
SCANNER-313) have the same shape as Jira keys (PROJ-123). The Discord bot extracted those tokens from sentry.io URLs and Sentry alert embeds, pinned them under Jira, and injectedjira: SCANNER-313into agent turns — so the agent treated an obvious Sentry issue as a Jira ticket.What
selectedIssueURLs are still extracted.Test plan
vp test runjiraLinks, sentryLinks, threadInfoPin, ThreadLinkStore, threadContext, MentionRouterapps/discord-bottypecheckhttps://*.sentry.io/issues/SCANNER-313should pin Sentry, not Jiraopened by Patrick Roza in chat thread Discord · what happened here?