We’re using OSLC Connect to sync test cases from Xray Test Management to Polarion ALM. Test cases are creating successfully in Polarion, but the requirement links aren’t coming through. In Xray, each test case has a “Requirement” custom field mapped to Jira requirements, but after sync these links are missing in Polarion’s traceability matrix.
We’ve verified the OSLC Connect artifact type mapping shows Test Case → Requirement as configured, and the Xray custom field for requirement links appears in the mapping settings. The sync logs show successful transfers but no errors about missing links.
This breaks our end-to-end coverage reporting since we can’t trace which requirements have test coverage. Has anyone dealt with cross-tool permission validation issues between Polarion and Jira that might block link creation?
The Xray “Requirement” custom field isn’t the same as Jira issue links. OSLC Connect reads Jira issue link types, not custom fields. In Xray, you need to use the native “Tests” or “Requirement” link type (found under “Link Issue” in Jira) rather than the custom field dropdown. If your team has been using the custom field, you’ll need to either migrate to proper Jira links or create a custom OSLC Connect transformer script that reads that specific custom field and creates the Polarion relationship programmatically.
Check if your OSLC Connect configuration has the correct relationship type mapping. The requirement link field in Xray needs to map to Polarion’s linked work items relationship, not just a custom field. Also verify that the Polarion user account used by OSLC Connect has permissions to create work item links across projects.
Thanks for the pointer. I checked the Related Artifacts section and found it was empty. Added a mapping from Xray’s “Tests” link type to Polarion’s “verifies” relationship. Ran a test sync with one test case but still no requirement link appeared in Polarion. The OSLC Connect logs show the test case sync but don’t mention attempting to create the relationship. Do I need to enable something in Xray’s custom field configuration to expose these links to OSLC?
I’ve seen this before. The issue is usually that Xray stores requirement links as Jira issue links, but OSLC Connect needs explicit mapping to Polarion’s relationship types. Go to OSLC Connect admin → Artifact Mappings → expand your Test Case mapping → check the “Related Artifacts” section. You need to map Xray’s requirement link type to Polarion’s “verifies” or “related to” relationship. Without this, links are ignored during sync even though test cases transfer successfully.