Importing Updated ReqIF Data into an Existing Requirement Set in Jama

Overview

This article addresses how to import updated requirements from a different tool (e.g., CodeBeamer) into Jama Connect without creating a separate set, while maintaining traceability to existing requirements initially imported from DOORS.

1. Problem Statement

✔ Original ReqIF data was imported from DOORS.
✔ Updated requirements were exported from CodeBeamer and imported into Jama, but they were created as a new set instead of updating the original requirements.
✔ The customer wants the updated requirements from CodeBeamer to be merged with the original DOORS set, maintaining traceability.

2. Why is DX Creating a New Set Instead of Updating Existing Items?

• DX relies on ReqIF IDENTIFIERs for synchronization, not field values like "Alt-Tool-ID."

• Since the new CodeBeamer import does not share the original ReqIF Exchange ID, DX treats it as a new dataset instead of an update.

• Conversation Mode in DX only works when the ReqIF files share an existing exchange history (which CodeBeamer lacks).

3. Workarounds to Merge Updated Requirements Instead of Creating a New Set

A. Using a Custom API Script for Synchronization

✔ Develop a script that "connects" the separately imported items by comparing unique IDs (e.g., Alt-Tool-ID).
✔ The script would:

• Identify matching items in Jama based on imported ReqIF Identifiers or another mapped field.

• Update existing items instead of creating duplicates.

• Use Jama's API to sync diffs between the new and existing requirements.

🔗 Reference: A similar script exists in the EESP (Engineering Enterprise Scripts Program) and can be adapted:
📌 EESP - Name Sync Application in Engineering

B. Manual Workaround (If No Script is Available)

1. Import the updated requirements as a new set.

2. Manually compare IDs from the old and new sets.

3. Use Jama’s “Merge” or “Sync” function to manually replace the old versions with updated ones.

4. Best Practices for Preventing This Issue in Future Imports

✅ Ensure all tools maintain the original ReqIF Exchange ID when exporting updates.
✅ Use a script or API-based solution to synchronize updates instead of creating duplicates.
✅ If using DX, verify that updates follow the same ReqIF history instead of introducing a new one.
✅ Engage with Jama Support or explore JCI (Jama Connect Interchange) for better handling of multi-tool integrations.

5. Conclusion

• DX relies on ReqIF Identifiers for synchronization, not external tool IDs.

• A script-based solution can match and merge requirements by using a mapped field like "Alt-Tool-ID."

• Manually syncing items in Jama is a workaround if automation is not available.

• JCI (Jama Connect Interchange) may be a better long-term solution for managing multi-tool requirement synchronization.