fix(atlassian): unify error message extraction across all routes#4135
fix(atlassian): unify error message extraction across all routes#4135waleedlatif1 merged 4 commits intostagingfrom
Conversation
…and Confluence routes Add parseAtlassianErrorMessage() to jira/utils.ts as single source of truth for parsing all 5 Atlassian error formats. Update 51 proxy routes (18 JSM, 5 Jira, 28 Confluence) to use it instead of hardcoded generic errors. Remove dead errorExtractor field from 95 Atlassian tool files — the compat loop in extractErrorMessage() already handles all formats without it. Consolidate duplicate parseJsmErrorMessage into a re-export from the shared utility. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
PR SummaryMedium Risk Overview Adjusts JSM request creation so when Cleans up tooling/docs metadata by removing Reviewed by Cursor Bugbot for commit 2c8eaa8. Configure here. |
- Remove debug logger.info for formAnswers in JSM request route - Restore user-friendly spaceId error message in Confluence create-page route - Restore details field in Jira write and update route error responses Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…ource Remove re-exports of getJiraCloudId, parseAtlassianErrorMessage, and parseJsmErrorMessage from jsm/utils.ts. Update all 21 JSM routes to import directly from @/tools/jira/utils per CLAUDE.md import rules. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
@greptile |
|
@cursor review |
Greptile SummaryThis PR unifies Atlassian error message extraction across 51 proxy routes (JSM, Jira, Confluence) by introducing a single Confidence Score: 5/5Safe to merge — all changes are error-handling improvements with no behavioral regressions on the happy path. All findings are P2 style suggestions. The core logic (parseAtlassianErrorMessage, errorExtractor removal, formAnswers fix) is correct, well-tested per the test plan, and backwards-compatible. No P0/P1 issues found. No files require special attention; the minor location concern for parseAtlassianErrorMessage in tools/jira/utils.ts is cosmetic. Important Files Changed
Reviews (1): Last reviewed commit: "regen docs" | Re-trigger Greptile |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 2c8eaa8. Configure here.

Summary
parseAtlassianErrorMessage()tojira/utils.tsas single source of truth for parsing all 5 Atlassian error formats (errorMessage,errorMessages[],errors[].title/detail, field-level errors object,message)"Request failed with status 400"stringserrorExtractor: 'atlassian-errors'field from 95 Atlassian tool files — the compat loop inextractErrorMessage()handles all formats without itparseJsmErrorMessageinto a re-export from the shared utilityTest plan
jira_search_issues) still extract errors via the compat loop