Product
Platform overview Requirements Architecture Tests Risk SBOM Traceability Releases Review Center Reports Approvals Integration Hub AI Traceability Industries Pricing
Resources
Why traceunified Guides Documentation Compare Security & compliance
Book a demo Try for free

Set up your first integration

From an empty Integration Hub to items moving between traceunified and Jira or GitHub — connection, collection, integration, first run, and the checks that prove it works.

This walkthrough takes you from an empty Hub to items moving in both directions. Each step is one screen; for the concepts behind it, follow the links.

1. Add a connection

Before you start An account in the other tool, and a credential for it with write access if the integration will push.

  1. Open Integration Hub → Connections and add a connection for Jira or GitHub.
  2. Enter the tool's address and the credential — an API token or OAuth 2.0 for Jira; a personal access token or OAuth 2.0 for GitHub.
  3. Save, and check the connection passes its health check.
  4. If the integration will push to the other tool, switch on the connection's write policy — every connection starts read-only.

Result The credential is encrypted and stored. The connection's change detection reads Webhook + poll if its account could register a webhook, or Poll if not — there is nothing to choose. See Connections.

2. Create a collection

  1. Open Collections and create one on your new connection.
  2. Choose the projects in scope, the artifact type, and the traceunified item type it maps onto.
  3. Map the fields, any picklist values that differ, the relationships you want to become trace links, and attachments and comments.

Result The collection knows what it is talking about on both sides, and fields the other tool requires to create an artifact are already accounted for. See Collections.

3. Create the integration

  1. Open Integrations and create one that runs your collection.
  2. In Artifact creation, choose which side may create records in the other.
  3. In Field flow, declare which way each field moves.
  4. In Routing, pair a traceunified project with a project in the other tool.
  5. In Filtering, narrow what crosses if not everything on the route should.
  6. In Conflict resolution, decide what settles a two-way field edited on both sides — before two people do it.

Result Everything that will move is declared. See Integrations.

4. Run it and check

  1. Press Run on its row. That starts the integration and runs its first cycle straight away.
  2. Open Activity. Setup problems lists anything still missing, each with its remedy; clear them.
  3. If Activity reports unattributed edits, map those accounts in Account mapping.
  4. Open Sync history to confirm the cycle read and wrote what you expected.
  5. After the first few cycles, open Trace coverage for the project and trace what arrived before it piles up.

Result Items are moving on the poll — and in seconds wherever a webhook is registered — with every inbound change attributed on its item.

Was this helpful?