fix: Update to 2025 Atlassian Cloud API - migrate to /search/jql endpoints#3
Open
kalifg wants to merge 1 commit intotom28881:mainfrom
Open
fix: Update to 2025 Atlassian Cloud API - migrate to /search/jql endpoints#3kalifg wants to merge 1 commit intotom28881:mainfrom
kalifg wants to merge 1 commit intotom28881:mainfrom
Conversation
…oints This commit addresses the breaking changes in Atlassian's Jira Cloud API where the legacy /rest/api/3/search endpoint has been removed and replaced with /rest/api/3/search/jql. These changes ensure compatibility with current API. API Updates Made: - Replace deprecated /rest/api/3/search with /rest/api/3/search/jql - Add fallback mechanism (GET → POST) for complex JQL queries - Implement proper URL encoding for JQL parameters - Enhanced error handling with API-specific context messages - Improve assignee parameter handling (email vs account ID) New Features: - Add get-my-issues tool for dedicated user-assigned issue retrieval - Add getMyAssignedIssues() method in JiraClient class - Enhanced JQL query construction with case-insensitive currentUser support Breaking Changes Fixed: - Resolves "The requested API has been removed" errors - Fixes assigned issue search functionality - Maintains backward compatibility for existing JQL queries Technical Details: - Updated searchIssues() method in jira-client.ts to use /search/jql - Added robust error handling for 401, 403, 404 HTTP responses - Enhanced logging for API debugging and troubleshooting - Updated documentation with 2025 API changes and new tool usage 🤖 Generated with Claude Code Co-Authored-By: Claude <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.
🚨 Problem
The MCP Jira server was failing with "The requested API has been removed" errors when trying to retrieve assigned issues or perform searches. This was caused by Atlassian's deprecation and removal of the legacy
/rest/api/3/searchendpoint in 2025.✅ Solution
This PR addresses the breaking changes in Atlassian's Jira Cloud API by migrating from the deprecated
/rest/api/3/searchendpoint to the new/rest/api/3/search/jqlendpoint, ensuring compatibility with current API requirements.🔧 API Updates Made
Core Search Endpoint Migration
/rest/api/3/search(deprecated/removed)/rest/api/3/search/jql(current 2025 API)Enhanced Error Handling
JQL Query Construction Improvements
currentUsersupport🆕 New Features
New
get-my-issuesToolassignee = currentUser() ORDER BY updated DESCNew
getMyAssignedIssues()Method📋 Files Changed
src/utils/jira-client.ts- Updated search endpoint and error handlingsrc/tools/issue-tools.ts- Added new tool and improved JQL constructionREADME.md- Updated documentation with 2025 API changes and new featurespackage-lock.json- Version bump to reflect API compatibility updates🧪 Testing
📚 Documentation Updates
get-my-issues🔄 Backward Compatibility
🚀 Impact
This update ensures the MCP Jira server continues to work reliably with Atlassian's evolving API while adding valuable new functionality. Users will no longer experience "API has been removed" errors and will have access to improved assigned issue retrieval.
🔗 References
🤖 Generated with Claude Code
Co-Authored-By: Claude noreply@anthropic.com