fix(jira): honor EpicKeyField when extracting issues - #9067
Merged
Conversation
EpicKeyField is already on Jira scope config and in the Config UI, but extractIssues never applied it, so Cloud/Parent Link epics stayed empty. Co-Authored-By: Cursor Grok 4.6 <noreply@example.com> Co-authored-by: Cursor <cursoragent@cursor.com>
klesh
approved these changes
Aug 21, 2026
klesh
left a comment
klesh
left a comment
Contributor
There was a problem hiding this comment.
LGTM
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
2 participants
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
EpicKeyFieldis already stored on Jira scope config and exposed in Config UI as the Epic Link field, butextractIssuesnever applied it. Epic keys were only taken from the legacyfields.epicobject, so Jira Cloud / Parent Link custom fields stayed empty at the tool and domain layers.This follows the same pattern as
StoryPointField/DueDateFieldin the same extractor.Changes
ScopeConfig.EpicKeyFieldfromAllFieldsepicKeyFieldinSubtaskConfigso changing the transformation setting triggers a full re-extract