Handling 32-Character Field Names in ReqIFz Imports

Overview

When importing a .reqifz file into Jama Connect, users may encounter issues where:

• Item Type names appear as random 32-character strings instead of recognizable names.

• Enumeration values are displayed incorrectly, also as 32-character strings rather than meaningful labels.

This issue makes mapping to Jama Connect Item Types difficult or impossible.

Issue Diagnosis

✔ The ReqIF format pulls the unique field names rather than user-friendly labels.
✔ Some ReqIF exports (e.g., from DOORS) generate unique IDs for enumeration values and item types.
✔ Mappings become unreadable when attempting to match item types to Jama Connect.

Solution and Workaround

1. Extracting Readable Field Names

✔ Use a script to generate a reference report.

• Richard Watson has developed a script that can extract readable field names from the DPA file associated with DOORS ReqIF exports.

• Contact support or your internal team to access a similar tool.

✔ Manually reference the Word template guide.

• If scripting is unavailable, download the word template reference guide before mapping.

• This document provides a reference for mapping Item Types and Enumeration values correctly.

2. Checking ReqIF Export Settings

✔ Verify the ReqIF definition/export settings in DOORS.

• The export settings might be generating unique field identifiers instead of user-friendly labels.

• If possible, adjust settings to include both the unique ID and the human-readable name.

✔ Generate different ReqIFz files using alternative export configurations.

• Some users have reported that different DPA files generate different ReqIFz outputs.

• If applicable, test multiple export settings.

3. Alternative Migration Strategies

✔ Consider an alternate tool for mapping.

• IBM DOORS Next and Dassault’s ReqIFzy were mentioned as options for evaluating better ReqIF compatibility.

• Evaluate which tool handles enumeration and item type mapping more effectively.

✔ Delay migration until more mapping tools are available.

• If your organization has long-term plans for migration, consider waiting until better tooling is developed.

Best Practices

✅ Before Exporting from DOORS: Test different ReqIF export configurations to determine which provides better field labels.
✅ During Import into Jama Connect: Use a script or template reference guide to cross-check field names.
✅ For Long-Term Migration Plans: Explore alternative tools like IBM DOORS Next or Dassault ReqIFzy for better mapping capabilities.

Conclusion

✔ The issue stems from ReqIF pulling unique field names instead of readable labels.
✔ Scripts and reference guides can help extract correct field mappings.
✔ Alternative ReqIF export settings or mapping tools may improve results.
✔ Evaluating different tools (e.g., IBM DOORS Next) could help with long-term migrations.