Limitations of the ReqIF Import

One of the main design goals of the ReqIF Import were providing the ability to load huge amounts data contained in ReqIF documents fast, accurately and reliably.

This goal require to make some compromises which are documented here.

Reliable Import

Importing the data in a ReqIF document is expected to work regardless of complex setting in the tracker configuration. To achieve that the ReqIF import will bypass following rules and proceed even if the data violates them:

• Permissions: Read-only fields will be set by the ReqIF Import.
• Mandatory Fields: Item will be created or update items even if not all mandatory fields are populated.
• Configured Reference Targets: References will be created even if the target item is not valid according to the reference configuration.
• Allowed Reference / Choice Values: Reference or choice values will be 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 will not be 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 following configuration options that potentially alter the imported data are not considered by the ReqIF import:

• 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.