Integrations

• Project import. Map organization, project, owner and dates from an existing project source into the corresponding records before importing requirements.
• Testing evidence. If the team connects a test system, agree how its results become project-linked findings and how supporting files attach to the relevant records.
• Work tracking. If the team connects a work tracker, use each requirement item’s task key to identify the matching work there. Keep that system’s own identifiers in that system.
• Time source. If hours originate elsewhere, agree how each person, project, work date and optional item will be entered before submitting time.

Agree which system owns each value before a connection is set up. Keep project and requirement references stable, check duplicate records during an import, and rehearse a changed revision before relying on a baseline decision. For attachments, review internal or shared visibility after import. Review operation receipts and failed entries when a connected action is retried so the team can tell which outcome belongs to which attempt.