ConnectALL support for SaaS Jira new pagination method (nextPageToken) replacing deprecated startAt

Products

• ConnectALL
• ConnectAll On-Prem

Issue/Introduction

Jira has announced changes to their REST API pagination model. The current startAt parameter is being deprecated, and a new token-based pagination method (nextPageToken) must be used instead. Our existing Jira integration relies on startAt for paging through query results. Without updating, future API calls may fail or return incomplete data once startAt is removed from Jira’s supported parameters.

 

https://developer.atlassian.com/changelog/#CHANGE-2046

 

Steps to Reproduce: 

1. Set up an automation to Jira SaaS that will trigger pagination

2. Run the automation

3. Review the logs

Expected Results: 

Connector should adopt the new pagination strategy:

• Use nextPageToken in request payload or query.
• Receive nextPageToken from each API response and use it in subsequent calls.
• Stop relying on startAt.

Actual Results:

Connector continues to rely on startAt. Depending on endpoint/version, this might still return partial results—but behavior is inconsistent and unsupported going forward.

 

Environment

All ConnectAll versions prior to 3.9.0.3

Cause

DE175040

Resolution

Upgrade to a version of ConnectALL 3.9.0.3 or higher