Repository navigation
fix(integrations): Use workflow URL exclusively in ticket descriptions - #127718
Open
sentry-junior[bot] wants to merge 1 commit into
Open
sentry-junior[bot] wants to merge 1 commit into
sentry-junior[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
added
the
Scope: Backend
Member
|
not strictly a ref. |
sentry-junior
Bot
force-pushed
the
kc/create-ticket-workflow-description
branch
from
October 16, 2026 00:43
e20d914 to
728fd23
Compare
sentry-junior
Bot
changed the title
This branch has not been deployed
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.
Ticket creation actions now always link the description footer to the workflow, even when a legacy rule ID is also present. The legacy rule URL builder is removed, and
build_description_workflow_engine_uiis renamed tobuild_description.When an action fires without a
workflow_id, we log<provider>.rule_trigger.missing_workflow_id(except for test notifications) and create the ticket with the group description but no footer, instead of falling back to the legacy rule URL. This matches how Opsgenie handles the same case.via @kcons.
--
View Junior Session [Sentry]