Hi Team,
We are using below rest call to pull the change log history, but we can't get complete history using this, it pulls only 100 change log records.
https://xxxxx.atlassian.net/rest/api/2/search?jql=issuekey=JA-8142&expand=changelog
Is there any way we can get complete change log history or any other workarounds.
We are on Jira Cloud.
TIA!
Dear @Ash ,
you can work-a-round by pulling the changelog directly instead of the search:
GET /rest/api/2/issue/JA-8142/changelog
So long
Thomas
Thank you @Thomas Deiler
Actually we use Jira filter to pull the data.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The limit of 100 cannot be extended for your rest function. You need to pull each changelog for each issue the filter call will return.
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.
Thank you for your reply.
This request GET /rest/api/2/issue/JA-8142/changelog
I see the same results with this call as well.
We use api to pull set of data from jira cloud to our Tablue to create reports. I don't think it is a good idea to pull the results using each issues key.
Still looking for the suggestions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @Ash ,
everything is fine with the above request. You have to paginate to get more. This limit has been hard coded to the rest api for cloud. There are no other ways as I have already described.
So long
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.