Jira Source connector - maxResults for paginated attributes

[lifegivesyoulemons]

Hi!
We are actively using the Jira source connector (many thanks to those developing and supporting it) to extract organization's data from Jira.

Our recent case is to extract the data on issue worklogs that are available both through issues and issue_worklogs streams. But by default only 20 worklogs per issue are available (and seems like it is hardcoded in the connector since the default in Jira docs is 5000).

It would be great to have an input parameter for this source to set maxResults that would be injected in different streams instead of being hardcoded.

[Aaron ("AJ") Steers (aaronsteers)]

Hi lifegivesyoulemons, thank you for this feature request and for the detailed explanation!

You are correct that the Jira source connector currently uses hardcoded page sizes for pagination. Specifically:

• The connector's paginator definitions in manifest.yaml use a hardcoded page_size: 50.
• When fetching issues via the issues stream (with fields: "*all"), the embedded worklog field within each issue response is limited to 20 worklogs by the Jira API default for nested fields — and there is currently no way to configure this.

Workaround: In the meantime, you can use the dedicated issue_worklogs stream, which properly paginates through all worklogs per issue via the Get issue worklogs endpoint. This stream uses the standard paginator and should return all worklogs rather than being limited to 20.

I have escalated this to the internal team for review: https://github.com/airbytehq/oncall/issues/11818

---

Need more help? Join Airbyte Community Slack for peer support, or if you're a Cloud customer, open a support ticket referencing this URL.