Release date US: 2025/12/15
Release date AU/EU: 2025/12/16
Jama Connect Interchange™ v1.31
Configuring Multiple Associated Mapping Groups (Excel Functions)
When configuring Excel Functions mappings, you can now add up to three associated mapping groups to a single base mapping group. This capability allows you to configure more complex logic that incorporates values from multiple item types or related items.
For example, in a base Risk item, you can populate a text box with a summary that pulls data from both related Hazards and related Harms. Alternatively, you can configure conditional logic where one scenario populates a field with data from one related item type, while another scenario populates the same field with a different related item type.
You can also consolidate logic that previously required multiple mapping groups into a single group.
For example, an auto-population scenario that previously required three mapping groups can now be consolidated into one. This can improve sync performance because the total number of field mapping groups in an integration directly affects sync processing time.
Before:
-
Base Risk item
- Related upstream Hazard
-
Base Risk item
- Related upstream Harm
-
Base Risk item
- Related downstream Verification
After:
-
Base Risk item
- Related upstream Hazard
- Related upstream Harm
- Related downstream Verification
This enhancement is available for both single- and multi-project Excel Functions integrations.
Minor Enhancements
- Bidirectional syncing for Jama Connect tags (Jira Cloud, Jira Data Center) — The Jira integration now supports bidirectional syncing of Jama Connect tags to Jira labels, single-select fields, multi-select fields, and text fields.
Resolved Issues
This release provides standard maintenance updates to deliver performance, security, and reliability improvements. Additionally, the following customer-reported issues were resolved.
| ID | Module | Description |
| SOS-DEF-9226 | ReqIF | During import, sets and folders are now assigned the correct item type (for example, "Set of Requirements," "Folder of Defects") based on the item type assigned to their child items. In previous isolated scenarios, sets and folders were assigned the incorrect item type, leading to errors during import. |
| SOS-DEF-9250 | ReqIF | When importing a subsequent version of a ReqIF file that included additional items, the additional items were not imported to Jama Connect. This only occurred if the ReqIF file included a tool-extensions section. This issue has been resolved. |
|
SOS-DEF-9262 SOS-DEF-9263 |
ReqIF | In isolated scenarios, valid ReqIF files failed to upload to Jama Connect Interchange. This occurred if the file contained certain syntactical elements that Jama Connect Interchange was unable to parse. |
Comments
0 comments
Please sign in to leave a comment.