The analysis view answers questions that span several hops of traceability, such as "which test cases cover the requirements derived from this stakeholder need?". You describe the path as a series of steps, each step being an item filter, and say which trace types connect one step to the next. Trace.Space then follows the traces and lays the result out as a tree table with one column per step.
The analysis view is marked Beta in the sidebar.
To open it, expand Analysis in the left sidebar and click Saved analyses. Saved analyses are listed in the tree; click New analysis at the bottom of the tree to start a new one.
Building an analysis path
The Analysis path panel at the top of the page holds the steps. A new analysis starts with one empty step.
In the step card, type a name in Edit step name, for example Needs. The name becomes the column header in the results.
Under Filters, click + and add the filters that define the items for this step, for example Item Type is Stakeholder need or Descendants of a folder. The card footer shows how many items match.
Under Visible attributes, choose which fields the results show for these items. ID and Heading are selected by default; the list also offers every attribute that the matching items have.
Click the + button (Add step) to add the next step and repeat.
Between two steps sits a connector with a trace dropdown. Leave it on Any trace to follow every trace, or pick the trace types and directions that must link an item in the previous step to an item in this one, for example is derived to.
Delete a step with the bin icon in its footer. The collapse icon at the right of the panel header shrinks the cards to chips so the table gets more room; click the pencil icon to expand them again.
Each step returns at most 1,000 items, and the result table shows at most 1,000 paths, so narrow the first step with filters if you work with large sets.
Reading the result table
Every step is a column and every row is one path through the data: an item from step 1 that is traced to an item from step 2, which is traced to an item from step 3, and so on. Where one item leads to several items in the next step, its cell is merged across those rows so you can see the fan-out. A path that stops early leaves the remaining cells empty, which is how you spot a gap, for example a requirement with no test case.
Each cell shows the attributes you chose for that step. Hover a cell to highlight the whole chain it belongs to, and click an item's ID to open it in the details sidebar. Items you do not have permission to read show as No access.
Saving and reloading
Click Save analysis in the page header and enter a name. The button is enabled as soon as there is an unsaved change. Saving an existing analysis keeps its name unless you type a new one. Saved analyses appear under Saved analyses in the sidebar, and opening one restores its steps, connectors and attribute choices.
If you leave the page with unsaved changes, a dialog asks whether to Discard them or save first.
Click the ... button on a saved analysis in the sidebar tree to Favorite it, Make public or Make private (only the creator can change this), Rename it, or Delete it. Deleting cannot be undone.
Letting AI build the path
You can also ask the AI chat to build an analysis for you, for example "Create an analysis from stakeholder needs to requirements to test cases". The chat proposes the analysis, and once you approve it, replies with a link to the saved analysis. See Working with AI.
For a two-set comparison without intermediate steps, the Traceability matrix may be simpler. For the trace types themselves, see Traceability.