Visure Data Exchange with Jama Connect via ReqIF

Preston Mitchell
Preston Mitchell
  • Updated

Published Date: September 12, 2025

Validated: Yes

Audience: Everyone

Products and Versions Covered:

  • Jama Connect® 

  • Cloud

  • Self-Hosted

  • Jama Connect Interchange™ 

  • ReqIF Module

  • Visure Requirements Platform (ReqIF integration context)

Summary

This article explains how to exchange or migrate data from Visure into Jama Connect® using ReqIF (Requirements Interchange Format). ReqIF enables the transfer of requirement structures, trace relationships, and attachments between tools.

It also highlights known limitations in Visure-to-Jama ReqIF exchanges and provides best practices to ensure successful migration and accurate data mapping.

Resolution

Best Practice

Best Practice

  • Limit scope: Only exchange or migrate relevant data. Identify and prioritize critical fields; migrating all fields is not required.
  • Label specifications: For large projects, label Visure specifications intended for migration (for example, append “ReqIF” to the specification name). This simplifies export selection.
  • Export comprehensively: When possible, include all relevant specifications in a single ReqIF export to preserve cross-specification traceability.

 

Exchange / migrating multiple specifications

Issue Solution

Visure Spec Folders

  • Problem: ReqIF export does not treat Visure Spec Folders as a separate type from Specifications.

  • Impact: Upon import, Visure Spec Folders cannot be mapped to Jama Connect Components while Specifications map to Sets.

  • Export only Specifications (exclude Spec Folders).

  • All Specs will import into Jama Connect as a “flat list.”

  • Recreate the hierarchy manually in Jama Connect using Components, then drag and drop Sets into the desired structure.

Mixed Item Types in Visure Specifications

Problem: ReqIF export does not differentiate requirement, test case, or risk item types.

Impact: Imported content cannot be mapped to distinct Jama item types automatically.

  1. Identify Jama item types that need to hold data from Visure (e.g., System Requirement, Architecture, Test Case).

  2. Select a primary Jama item type for import (commonly Requirement) and ensure it includes all fields necessary for data mapping.

  3. Import all Visure Specs into this primary type.

  4. Convert Jama Sets into the appropriate Jama item types after import.

  5. Remove any temporary/custom fields used for mapping once conversion is complete.

 

Rationale: Splitting the migration into multiple ReqIF files per item type breaks traceability across specifications.

Implementation

Data discovery: Analyze Visure to identify specifications, structures, and fields required for migration.Label specifications: Clearly mark or document specifications intended for ReqIF export.Prepare ReqIF export:

  • Install and open the Visure ReqIF Plugin.
  • Select the identified specifications and fields.
  • Export and download the ReqIF file.

Import into Jama Connect:

Additional Resources

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.

Related to

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.