We have observed that when using the expand parameter in the Jira Search JQL API to fetch the changelog history associated with an issue entity, the result is limited to only 40 records. However, according to the Jira documentation :https://community.atlassian.com/forums/Jira-questions/Rest-API-limiting-changelog-history-results-to-100-even-if/qaq-p/1466525
, it is stated that up to 100 changelog records can be retrieved.
Is this limitation imposed by Jira SaaS? If so, could you provide an official link confirming this? Additionally, is there any option to retrieve more than 40 changelog records for an issue entity using the Jira Search JQL API ?
For reference, we are using the following URL to fetch the changelog history associated with the issue entity:
https://api.atlassian.com/ex/jira{JiraCloudId}/rest/api/3/search/jql?expand=changelog
Hi @AppFlow I found JRACLOUD-96459 on Atlassian's Jira Sie which sounds like your issue.
I would suggest voting for and watching it for updates. It was recently reported.
I'm also going to ping Support, because if the link you referenced referred to 100 rows returned, there seems to be a discrepancy that could use some clarification.
Hope that helps.
Hi @AppFlow
Yes, and...to the information from @Dan Breyen
In the Developer Community RFC for the new search, I recall Atlassian noted the returned changelog count was limited, independently of the maxResults selected for the work item search itself. They stated to get more changelog entries, the separate changelog get endpoint should be used for each work item, either up to 100 or with the bulk-get.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.