Creating links

Building the thread means creating links between items. A link is quick to make and precise in meaning, and the platform keeps it valid so the thread stays trustworthy as it grows.

Linking two items

From an item, you link it to an existing item and choose the relationship type that describes the connection. That’s the whole act: pick the target, pick the relationship, and the link becomes part of both items’ records and part of the thread. Because the link is a record, it carries its own history — who made the connection and when.

Rules keep the thread valid

Not every relationship makes sense between every pair of item types — a test verifies a requirement, but it wouldn’t satisfy one. TraceUnified applies the relationship rules your organization has configured, offering only the relationship types that are valid for the items involved. This keeps the thread meaningful: you can’t accidentally assert a connection that doesn’t make sense in your process.

Both directions at once

A link is directional, but it’s visible from both ends. Create a “verified by” link from a requirement to a test, and the requirement shows the test that verifies it while the test shows the requirement it covers. You only make the connection once, and both items reflect it — there’s no separate reverse link to maintain.

Linking across projects

Some relationships cross project boundaries — a product variant that reuses a platform requirement, or a shared component referenced from several projects. Where your process allows it, links can connect items across projects, so the thread reflects how your work actually depends on itself rather than stopping at a project’s edge.

Keeping links honest

A link asserts that two things are related, and the platform keeps that assertion live. When one side changes, the other can be flagged for review rather than silently going stale — the mechanism covered in Suspect links. Creating good links is the investment; live coverage and impact analysis are the return.