Feature/cmg 705

[aishwarya-cstk]

🔗 Jira Ticket

Replace with your ticket link — required before requesting review.

(https://contentstack.atlassian.net/browse/CMG-923)(https://contentstack.atlassian.net/browse/CMG-920)

---

📋 PR Type

• ✨ Feature
• 🐛 Bug Fix
• 🔥 Hotfix
• ♻️ Refactor
• 🧹 Chore / Dependency Update
• 📝 Documentation

---

📝 Description

What changed?

• Fixed an issue in WordPress 2.0 → New Stack flow where field data was incorrectly shown as missing when changing the field type from Single Line Text to Multi Line Text for:

  • Test Entry → Media & Text

• Fixed an issue in WordPress 2.0 → Existing Stack flow where data was not being populated for the following Story Block fields:

  • Alt
  • Caption

Why?

These issues caused migrated content to appear incomplete in the field mapping UI despite the source data being available. The fixes ensure field values are correctly retained and displayed during migration validation and mapping workflows.

---

🧩 Affected Areas

• api — Node.js backend
• ui — React frontend
• upload-api — Upload API server
• docker / docker-compose
• CI / GitHub Actions workflows
• Environment variables / config
• Other:

---

🧪 How to Test

Scenario 1: New Stack Flow

1. Create or open a WordPress 2.0 migration project using the New Stack flow.
2. Navigate to Test Entry → Media & Text.
3. Map a field as Single Line Text.
4. Change the field type to Multi Line Text.
5. Verify the field data is still displayed correctly and is not marked as missing.

Scenario 2: Existing Stack Flow

1. Create or open a WordPress 2.0 migration project using the Existing Stack flow.
2. Navigate to Test Entry.
3. Open the Story Block field mapping.
4. Verify that Alt and Caption fields display the migrated source data correctly.

Expected result:

• data is not missing when changing field types from Single Line to Multi Line Text.
• Story Block Alt and Caption fields correctly display the available source data.

---

🔗 Related PRs / Dependencies

• None

---

✅ Author Checklist

• Branch follows naming convention: feature/, bugfix/, or hotfix/ + 5–30 lowercase chars
• Jira ticket linked above
• Self-reviewed the diff — no debug logs, commented-out code, or TODOs left in
• .env / example.env updated if new environment variables were added
• No sensitive credentials or secrets committed
• Existing tests pass locally (npm test)
• New tests written (or not applicable — explain why)
• README.md / docs updated if behaviour changed
• Talisman pre-push scan passes (no secrets flagged)

---

👀 Reviewer Notes

Please focus on:

• Field type switching behavior for text fields in the New Stack migration flow.
• Story Block field mapping and data population for Alt and Caption fields in the Existing Stack migration flow.
• Regression checks for other text-based field mappings.

---

Migration v2 · Docs · Issues

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	0	0	10	✅ Passed
🟠 High Severity	15	334	25	✅ Passed
🟡 Medium Severity	20	3	500	✅ Passed
🔵 Low Severity	0	0	1000	✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	2	90 / 365 days	⚠️ Warning
🔵 Low	0	0	180 / 365 days	✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

• Critical without fixes: 0
• High without fixes: 334
• Medium without fixes: 3
• Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	0	0	10	✅ Passed
🟠 High Severity	15	334	25	✅ Passed
🟡 Medium Severity	20	3	500	✅ Passed
🔵 Low Severity	0	0	1000	✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	2	90 / 365 days	⚠️ Warning
🔵 Low	0	0	180 / 365 days	✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

• Critical without fixes: 0
• High without fixes: 334
• Medium without fixes: 3
• Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.