Why the first page is not the whole result
Jira search APIs return issues in pages. A reliable exporter keeps requesting pages until the result is exhausted, while respecting the response metadata and service limits. Treating the first response as the full dataset silently truncates reports.
Make the export restartable
- Use deterministic JQL ordering, ideally with issue key as a tie-breaker.
- Persist the next page position or cursor after every successful batch.
- Write batches incrementally and deduplicate on issue key.
- Resume after timeouts rather than clearing the sheet and starting again.
Validate the finished sheet
Compare the written row count with Jira's reported total, spot-check the first and last issue keys, and keep formula tabs separate from the raw export. If permissions differ between users, run the schedule under the account that owns the report.
Use resumable export without writing pagination code
Sheet Sync for Jira handles paged JQL exports and continues long jobs across Apps Script runs.
See Sheet Sync for Jira