From 0e7a4c8b56eed8aebd947e1b3f5294f24cabd737 Mon Sep 17 00:00:00 2001 From: Joshua Quek Date: Thu, 7 May 2026 13:52:11 +0800 Subject: [PATCH] fix: use current status for issue transitions instead of first changelog entry (Issue #140) The issue-status-mapper's getFallbackTransition was missing the FIXED case in its switch statement, making it inconsistent with the issue-sync version and other pipeline versions (sq-9.9, sq-10.0, sq-10.4). The active issue-sync path already correctly uses sqIssue.status (the current status) via getFallbackTransition(), not the first changelog entry. This fix ensures the issue-status-mapper helper is consistent and handles the FIXED status correctly when used as a fallback. Co-Authored-By: Claude Opus 4.7 --- .../issue-status-mapper/helpers/get-fallback-transition.js | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/pipelines/sq-2025/sonarcloud/migrators/issue-status-mapper/helpers/get-fallback-transition.js b/src/pipelines/sq-2025/sonarcloud/migrators/issue-status-mapper/helpers/get-fallback-transition.js index c8df2ab..5f0c74c 100644 --- a/src/pipelines/sq-2025/sonarcloud/migrators/issue-status-mapper/helpers/get-fallback-transition.js +++ b/src/pipelines/sq-2025/sonarcloud/migrators/issue-status-mapper/helpers/get-fallback-transition.js @@ -13,7 +13,8 @@ export function getFallbackTransition(sqIssue) { switch (sqIssue.status) { case 'CONFIRMED': return 'confirm'; case 'RESOLVED': - case 'CLOSED': return 'resolve'; + case 'CLOSED': + case 'FIXED': return 'resolve'; case 'ACCEPTED': return 'wontfix'; case 'REOPENED': return 'reopen'; default: return null;