fix(jira): migrate Cloud search to v3 API endpoint #769
Conversation
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
The Jira Cloud v2 search API (/rest/api/*/search) has been deprecated and is now returning errors. This commit migrates Cloud deployments to the new v3 search endpoint (POST /rest/api/3/search/jql). Changes: - Cloud: Use POST /rest/api/3/search/jql with nextPageToken pagination - Server/DC: Continue using the v2 /rest/api/2/search endpoint unchanged - Updated tests to mock the new v3 API calls for Cloud scenarios The v3 API has some differences: - Uses JSON body instead of query parameters - Uses nextPageToken for pagination instead of startAt - Does not return total count (returns -1) - Max 100 results per request (was 50 for Server/DC) Fixes #720 Github-Issue:#720
jfugalde
added a commit
to jfugalde/mcp-atlassian
that referenced
this pull request
Dec 3, 2025
Updated the JiraConfig class to support optional prefixes for environment variables, allowing for more flexible configuration. This change includes: - Added a `prefix` argument to the `from_env` method to customize environment variable names. - Updated environment variable retrieval to use the specified prefix where applicable. - Improved error messages for missing required variables, ensuring clarity on which variables are needed. This enhancement facilitates better integration in environments with multiple configurations, such as testing or deployment scenarios. Fixes sooperset#769
nszceta
pushed a commit
to nszceta/mcp-atlassian
that referenced
this pull request
Dec 4, 2025
The Jira Cloud v2 search API (/rest/api/*/search) has been deprecated and is now returning errors. This commit migrates Cloud deployments to the new v3 search endpoint (POST /rest/api/3/search/jql). Changes: - Cloud: Use POST /rest/api/3/search/jql with nextPageToken pagination - Server/DC: Continue using the v2 /rest/api/2/search endpoint unchanged - Updated tests to mock the new v3 API calls for Cloud scenarios The v3 API has some differences: - Uses JSON body instead of query parameters - Uses nextPageToken for pagination instead of startAt - Does not return total count (returns -1) - Max 100 results per request (was 50 for Server/DC) Fixes sooperset#720 Github-Issue:sooperset#720
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 Jira Cloud v2 search API (
/rest/api/*/search) has been deprecated and is now returning errors indicating users should migrate to the v3 API.This PR migrates Cloud deployments to the new v3 search endpoint.
Changes
POST /rest/api/3/search/jqlwithnextPageTokenpagination/rest/api/2/searchendpoint unchangedv3 API Differences
startAtoffsetnextPageTokentokenTest Plan
Related