Handle Jira Server/Data Center Issue pagination
What does this MR do and why?
As identified in #591597 (closed), the Jira Server importer wasn't handle batch sizes greater than 1,000 issues. Imports with greater than this count of issues would quietly fail on issue 1,001, and would impact the MR IID as the system would still be trying to assign an issue to these missed issues.
Thanks to @acroitor's patch file, the fix is straightforward to ensure the pagination state is aware of the proper page count.
To-Do
- Update Specs
- Review Duo's suggestion on if this will break Jira Cloud
References
Screenshots or screen recordings
Scenario: 2,097 issues on Jira.
| Before | After |
|---|---|
 |
 |
| MR IIDs continued to climb, as originally reported, even though imports stopped after 1,000. | MR IIDs worked as normal, making the new IID follow on after the imports. |
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Edited by Ben King