OJ-53536 Handle Jira Server pagination bug truncation - #442
Merged
Conversation
Some versions of Jira Server limit the user search to the pagination limit of the server, so we will get back different users and different counts, but only ever out of the first X matching users. This was making us miss cases where we needed to fall back to an alphabetical lookup. This version bump includes logic to check for that case. We will now look ahead X results if we get back a 10, 100, or 1000 result set for users. We'll trigger the alphabetical lookup if the lookahead doesn't return results.
dregalbuto
approved these changes
Mar 27, 2026
|
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
2 participants
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.
Some versions of Jira Server limit the user search to the pagination limit of the server, so we will get back different users and different counts, but only ever out of the first X matching users. This was making us miss cases where we needed to fall back to an alphabetical lookup. This version bump includes logic to check for that case. We will now look ahead X results if we get back a 10, 100, or 1000 result set for users. We'll trigger the alphabetical lookup if the lookahead doesn't return results.