Export Jama requirements as one inventory and review history as another. A tabular item export is useful for current fields, while relationships, test evidence, attachments and approval context may need separate treatment. The aim is a reconciled package, not a claim that every source behaviour can be recreated automatically.
Which project slice should we export?
Choose an approved requirement set with parent-child structure, cross-item relationships, a review and a linked test. Record the Jama item type, global ID, project, fields, baseline and relationship rules. Set the source read-only for the trial or record a precise export timestamp and change freeze.
Which documented outputs are available?
Jama's Excel export works on selected content, and Jama warns about rich-text formatting and spreadsheet interpretation of values beginning with an equals sign. Do not assume the visible columns contain every attribute. Review exports provide activity or version reports as Word or PDF. Decide whether each report is an archive record or whether a destination workflow needs a new current review.
How do we inventory the relationships?
Capture each relevant source ID, target ID, relation type and direction, including test relationships. Count them separately from item rows. Inventory attachments and references to external tools. Map item types and status values to destination semantics; do not silently turn a Jama review status into an engineering acceptance decision.
How do we validate the destination?
Import a small slice using the destination's confirmed path, inspect text and IDs, and traverse each selected relationship in both directions. Attach or retain the review archive according to the retention policy. Have the requirement owner and verification lead sign off exceptions and establish the new baseline only after these checks pass.
What should the Arc import preserve?
Arc's approved direct inputs are CSV, Word, Jira, Git and Confluence; a native Jama adapter is not claimed. Confirm an export and mapping route for the actual source configuration. Arc review and change features govern new work, while historical Jama decisions need an explicit archive or reconstruction plan.
Frequently asked questions
Does an Excel export include Jama review history?
No such assumption is safe. Jama documents separate review exports; inventory and retain the relevant activity or version records.
What should be counted separately?
Requirement items, relationships, attachments, tests and review records should each have a source and destination reconciliation.
Can Arc import Jama natively?
A native Jama adapter is not in the approved direct import list. Agree and test a supported export and mapping path.
Evaluate a representative import in Arc
Agree the record mapping and reconciliation for a representative source package. Arc connects accepted requirement records to system context, controlled changes and verification evidence.
Luc will email from luc@archelps.com to arrange setup. Agree scope and data handling before adding programme information.