fix: fetch real issue metadata in webhook replay script#72
Open
JoshSalomon wants to merge 1 commit into
Open
Conversation
The test payloads hardcode issuetype as "Feature", which bypasses parent routing for Epics/Tasks. The script now fetches the real issue type, labels, summary, and status from Jira and injects them into the payload, so child ticket events route correctly. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.
Summary
The webhook replay script (
devtools/run-wh.sh) hardcodesissuetype: "Feature"from the test payloads. When targeting Epics or Tasks, this bypasses the parent routing logic — the webhook handler never checksforge:parentlabels, so child ticket events are processed as standalone Features.The script now fetches the real issue type, labels, summary, and status from Jira and injects them into the payload before sending.
What changed
GET /rest/api/3/issue/{key}?fields=issuetype,labels,summary,statusissuetype,labels,summary,statusinto the payloadTest plan
devtools/run-wh.sh AISOS-741(Feature) — payload showsissuetype: "Feature"devtools/run-wh.sh AISOS-751(Epic) — payload showsissuetype: "Epic", routes to parent🤖 Generated with Claude Code