Fixing Empty Description Fields in Jama-to-Jama ReqIF Migration (DX 3.9.1 Bug)

Overview

This article addresses an issue where description fields do not migrate correctly during a Jama-to-Jama ReqIF exchange using DX 3.9.1, leading to the error:
✔ "ERROR | Unable to get original xhtml content"
✔ The description field appears empty in the target project.

Resolved in DX 3.9.2.

1. Issue Summary

✔ A defect in DX 3.9.1 caused description fields to fail migration.
✔ The ReqIF file appeared correct, but the description field did not transfer to the target project.
✔ The DX log contained an error indicating failure to parse XHTML content.

2. Solution: Update to DX 3.9.2

✔ DX 3.9.2 contains a patch that fixes the issue.
✔ After updating, description fields now migrate correctly.
✔ Users who tested DX 3.9.2 confirmed that the descriptions appeared as expected.

🛠 Steps to Upgrade DX:

1️⃣ Download the DX 3.9.2 update.
2️⃣ Replace the existing DX installation with the updated version.
3️⃣ Re-run the ReqIF import/export process.
4️⃣ Verify that descriptions appear correctly in the target Jama project.

3. Best Practices for Debugging ReqIF Description Issues

✅ Check DX Logs for XHTML Parsing Errors:

Look for errors similar to:
✔ "Unable to get original xhtml content"

✅ Verify the ReqIF File for Description Data:

Open the exported ReqIF in a text editor and search for <text> fields.
If missing, the issue originates from the export process.

✅ Test in DX 3.9.2 or Later Before Production Use:

Run a small-scale migration first to confirm the fix.

✅ Ensure All Required Fields Are Mapped Correctly:

Review DX mapping settings before export/import.

4. Conclusion

✔ DX 3.9.1 had a bug that prevented descriptions from migrating correctly.
✔ This issue is resolved in DX 3.9.2.
✔ Users should update to DX 3.9.2 and retest migrations.

Fixing Empty Description Fields in Jama-to-Jama ReqIF Migration (DX 3.9.1 Bug)