Repository navigation
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Bundles Sizes Evolution
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ccb8365d4a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - The Atlassian MCP create call only takes the summary and a plain-text description: set the other fields right after with an update, and write the description in Atlassian Document Format so headings, lists and links render (add the Log Explorer links once the key exists). | ||
| - After creation, use the new key as the pipeline category name. | ||
| - Closing or reopening a ticket follows the same rule: show the transition and the comment (reason, 24h count or fixed version) and apply it only after approval. | ||
| - Closing or reopening a ticket also moves its pipeline category to the matching status: won't do, done (pinned to the versions before the fix) or, when reopening, needs investigation. Show the transition, the comment (reason, 24h count or fixed version) and the category move, and apply each only after approval. |
There was a problem hiding this comment.
Revalidate the version pin when reopening
issue: When a Done ticket is reopened because the fix did not hold on newer SDK versions, merely moving its existing category to needs investigation preserves the Done query's old pre-fix version pin. The recurring errors will therefore remain untagged and absent from the known-issue sample even though the ticket is open again. Explicitly require updating or removing the stale pin when moving a Done category back to needs investigation.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
More details
The close/reopen instruction preserves approval for each Jira and pipeline write and requires fixed-issue categories to remain pinned to pre-fix versions. The completed static review found no reportable defect.
🤖 Bits Code Review · Commit ccb8365
🎉 All green!🧪 All tests passed 🎯 Code Coverage (details) 🔗 Commit SHA: 4827fdd | Docs | View more details | Give us feedback! |
Motivation
Follow up to #5169. When the triage skill closes or reopens a ticket, it only does the Jira transition. The Confluence page says the pipeline category moves too, so a Done ticket can keep its logs tagged as needs investigation.
Changes
The close and reopen step now also moves the pipeline category to the matching status, and shows it for approval like the transition. It is one line in
.claude/skills/triaging-telemetry-errors/SKILL.md. I drafted the wording with an AI agent, please review.Test instructions
Checklist