fix: migrate to /rest/api/3/search/jql endpoint #23
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
Fixes the 410 error from deprecated
/rest/api/3/searchendpoint by migrating to the new/rest/api/3/search/jqlAPI as per Atlassian's migration guide.This fixes the
ji minecommand which was failing with:Changes
searchIssues()to use/rest/api/3/search/jqlendpointsearchIssuesEffect()to use/rest/api/3/search/jqlendpointfields=*navigableparameter (matching old API default)totalandstartAtin responsesTesting
Tested with:
ji mine- works with pretty colored outputji mine --xml- works with XML outputji mine --status "In Development" --since 7d- works with filtersBackground
The new endpoint is required as of May 2025 when the old search endpoints were deprecated and progressively shut down starting August 2025.