Repository navigation
fix(jira): collect full changelog for issues truncated by the search API - #9377
Merged
Merged
Conversation
klesh
approved these changes
Nov 14, 2026
klesh
left a comment
klesh
left a comment
Contributor
There was a problem hiding this comment.
Good catch.
Thanks for your contribution.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Since #8931, Jira Cloud issues are collected via
/rest/api/3/search/jql?expand=changelog, which embeds only the newest 40 changelog histories per issue (the agile endpoint used before returned up to 100).collectIssueChangelogsstill fetched the full changelog only for issues withchangelog_total > 100, so issues with 41–100 histories silently lost everything older than the newest 40, including their first status transitions.This PR lowers the threshold to 40.
Does this close any open issues?
None.
Screenshots
N/A
Other Information
extractIssues→collectIssueChangelogs→extractIssueChangelogschain against a fake Jira Cloud server on MySQL 8.4. Before the fix, issues with 41, 60 and 100 histories kept 40; after it, all histories are stored, also on an incremental run. Issues with up to 40 or more than 100 histories, and epics, behave as before.fullSyncrun ofcollectIssueChangelogs+extractIssueChangelogs.