ReqIF Limitations
One of the main design goals of the ReqIF Import were is providing the ability to load huge amounts data contained in ReqIF documents fast, accurately and reliably.
This goal requires some compromises to be made which are documented here.
Reliable Import
Importing the data in a ReqIF document works regardless of complex settings in the tracker configuration. The ReqIF import bypasses the following rules and proceeds as described, even if the data violates those rules:
• Permissions: — Read-only fields are set by the ReqIF Import.
• Mandatory Fields: — Items are created or updated even if not all mandatory fields are populated.
• Configured Reference Targets: — References are created even if the target item is not valid according to the reference configuration.
• Allowed Reference / Choice Values: — Reference or choice values are set even if the value is not allowed to the status- or dependency-based configuration of allowed values.
• Workflow Transition Guards and Conditions: — Guards in workflow transitions are not considered when creating or updating items.
Accurate Import
An accurate import should represent the data as it was represented in the ReqIF. To avoid inaccuracies, the ReqIF import does not consider the following configuration options that potentially alter the imported data:
• Workflow Transition and Change Handler Actions — Action will not be executed.
• Listeners — Listeners will not be triggered.
• Distribution- and Aggregation-Rule — Field content will not be altered based on Aggregation- and Distribution-Rules.
• Default Values — Default values will not be set, even if field is empty.
Performant Import
ReqIF documents potentially contain thousands of items still the import is expected to be fast. Any additional processing of imported data will slow down the import. The ignored rules mentioned above also help to guarantee high import performance.