Exchange Support Between Jama and Polarion via DX

Overview

This article provides guidance on what works and what does not when exchanging data between Jama Connect and Polarion via Data Exchange (DX), including hierarchy considerations, item types, and known gaps.

1. Status of Jama-Polarion Exchange Support

✔ No comprehensive support documentation exists yet, but some migration work has been done.
✔ Internal documentation is being developed here:

• Freedom / Efficiency of operation	Connections	comments
  Best	In addition to everything in OK…. Read access to application server file system - to be able to read system.log	if possible, VPN access is fine for server access
  OK	Admin access to the polarion application with write permission Defined process for changing polarion configuration if needed Admin access to Jama Defined process for changing jama config if needed Data Egress under user's control Egress via sharepoint / onedrive or similar	VPN access needed to access the polarion application Check VPN software works with user's environment (eg, Mac compatible?) enables debugging & autonomous working enables changes to data model if needed Autonomous egress path to enable efficient working net access to sftp or similar could work
  Might Work	user executes scripts & sends data back via email	in theory one should have able to have the customer run the tools in the toolkits and just send us csv files Not tested that or documented it well enough to try as of 2022-05-15

✔ Main Areas of Concern:

• Hierarchy and Item Types

• Images and Attachments

• Specification Type Mapping

2. Key Considerations for Exchanging ReqIF Data Between Jama and Polarion

A. Hierarchy and Item Types

✔ Polarion requires strict hierarchy management.
✔ Avoid mixed item type hierarchies in Polarion (e.g., combining folders and text in the same set).
✔ Jama's flexibility in text/folder usage may not transfer well into Polarion.

B. Specification Type Mapping

✔ Spec-object type should be used for item type mapping rather than relying solely on hierarchy structure.
✔ Mapping specifications correctly ensures better compatibility.

C. Images and Attachments

✔ Polarion may not fully support all attachment types in ReqIF.
✔ Embedded images inside rich text fields may not transfer properly.
✔ Separate image files should be checked for proper linking.

3. Workarounds for Improving Jama-Polarion Exchange

✔ Ensure that item types align before import/export.
✔ Use structured hierarchies in Polarion rather than mixed sets.
✔ Validate image and attachment handling post-import in Polarion.
✔ Monitor JCI development, as it may handle tool-specific ReqIF solutions better.

4. Best Practices for Jama-Polarion Exchange via DX

✅ Follow structured hierarchy rules in Polarion to prevent misalignment.
✅ Test small ReqIF samples before full-scale exchange.
✅ Check whether images and attachments transfer correctly.
✅ Refer to specification type instead of relying on spec-object type for item mapping.

5. Conclusion

• Jama-Polarion exchange via DX is possible, but requires structured data handling.

• Hierarchy and item type consistency are critical for a smooth exchange.

• Images and attachments may require manual validation post-import.

• Future JCI developments may improve ReqIF handling for tool-specific needs.