mfrancisc opened a new pull request, #9067: URL: https://github.com/apache/devlake/pull/9067
### Summary `EpicKeyField` is already stored on Jira scope config and exposed in Config UI as the Epic Link field, but `extractIssues` never applied it. Epic keys were only taken from the legacy `fields.epic` object, so Jira Cloud / Parent Link custom fields stayed empty at the tool and domain layers. This follows the same pattern as `StoryPointField` / `DueDateField` in the same extractor. ### Changes - Map `ScopeConfig.EpicKeyField` from `AllFields` - Include `epicKeyField` in `SubtaskConfig` so changing the transformation setting triggers a full re-extract - Unit tests for string, object, legacy fallback, and empty-config (no accidental overwrite) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
