IE 1122 update deprecated jira apis #20
Merged
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
ananta0799
reviewed
Jul 29, 2025
ananta0799
reviewed
Jul 29, 2025
Theotata
reviewed
Jul 29, 2025
ajitkantata
reviewed
Jul 30, 2025
| stub_request( | ||
| :get, | ||
| site_url + '/jira/rest/api/2/search?jql=id IN(10001, 10000)' | ||
| 'http://foo:bar@localhost:2990' + '/jira/rest/api/3/search/jql?jql=id IN(10001, 10000)' |
b6b
approved these changes
Jul 30, 2025
Collaborator
b6b
left a comment
b6b
left a comment
There was a problem hiding this comment.
Overall it seems reasonable to me. I like adding a separate path we are just using for search. Just one question on naming.
In the future we can probably consolidate this back into one path if we want to fully upgrade to v3.
ananta0799
reviewed
Jul 31, 2025
b6b
added a commit
that referenced
this pull request
Aug 1, 2025
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.
Updated the jira search deprecated APIs to the new apis provided by Atlassian,
https://developer.atlassian.com/changelog/#CHANGE-2046.
Also please note this statement mentioned in the changelog
We’ll replace random page access with a continuation token API. This means you won’t be able to get multiple pages at the same time with parallel threads. startAt parameter will be replaced with nextPageToken.This means that the client of this jira-ruby gem can't use the
startAtparameter but needs this gem to send thenextPageTokenin response and subsequently that token will be used by the client to fetch the successive pages in their requests. So if you are back from future because of any error, might want to take a look at this info. 😄