Collections
Define what you are syncing — the tool, its projects, the artifact type, and the traceunified item type it maps onto — and map its fields, values, relationships and attachments.
A collection is a group of artifacts from one tool and the model they map onto. It is four facts:
- the tool its artifacts come from, through a connection;
- which of that tool’s projects are in scope;
- which artifact type — a Jira issue type, a GitHub issue;
- which traceunified item type those artifacts become.
One collection can be run by several integrations. Because traceunified is always one end of every integration, your item type is the shared model: there is no separate canonical model to maintain.
Map the fields
Field mapping pairs each field of your item type with the field it corresponds to in the other tool — Title with Summary, Status with status, and so on.
- The screen checks which fields the other tool requires to create an artifact, so a missing one is found while you configure, not as a failed write.
- Value maps translate picklists whose values differ between the two sides, so High here can be P1 there.
Map relationships
Relationship mapping pairs your trace relationships with the other tool’s link types. A link drawn in the other tool becomes a real trace link in traceunified only where the collection maps that relationship — the Hub never invents a trace rule. What arrives this way is a real trace, with the same suspect propagation and coverage as any other.
Map attachments and comments
Widget mapping pairs traceunified’s attachments, comments and relationships with whatever the other tool calls its equivalent. Which way each of these moves is decided per integration, in Widget flow.
Who can open it
Collections are organisation-wide integration configuration, and are available to organisation administrators.