Skip to main content

​
Overview

When a downstream item (such as a mitigation task or control measure) is linked to multiple sub-items, you can configure a clickable link that opens those relationships in a dedicated nested risksheet. This keeps complex traceability visible while maintaining a clear separation between parent and child risk contexts. diagram

​
Configuration Steps

​
1. Create the Nested Risksheet Document

Create a separate Polarion document that defines the structure for your nested view. For example, if your main risksheet shows risks and their control measures, create a document (e.g., Risks/Mitigations) that shows control measures as rows with their linked requirements as downstream items.

​
2. Configure the Nested Document Structure

Edit the nested document’s risksheet.json configuration to define:
  • Main row items: The work item type that appears as rows (e.g., risk controls)
  • Downstream items: The child items linked to each row (e.g., requirements)
{
  "dataTypes": {
    "task": {
      "type": "riskControl",
      "role": "mitigates",
      "name": "Risk Control",
      "zoomColumn": "taskTitle"
    }
  }
}
In your main risksheet configuration, add the linkToRisksheet property to the downstream data type and specify the target document path: 
{
  "dataTypes": {
    "task": {
      "type": "riskControl",
      "role": "mitigates",
      "name": "Risk Mitigation Measure",
      "zoomColumn": "taskTitle",
      "document": "Risks/Mitigations",
      "linkToRisksheet": true
    }
  }
}
The document property must match the exact space and document ID path of your nested risksheet. Incorrect paths will result in broken links or “document not found” errors.

​
4. Add a Clickable Column

In your main risksheet’s column configuration, create a column that binds to the downstream item. The link icon will automatically appear when linkToRisksheet is enabled: 
{
  "header": "Control Measure",
  "bindings": "task.$item",
  "width": 200
}
The risksheet will render the item with a clickable link icon. Clicking opens the nested risksheet filtered to show that specific item and its relationships.

​
5. Optional: Display Sub-Items with Server Rendering

To show a preview of nested items directly in the main risksheet (e.g., all requirements linked to a control measure), add a serverRender column: 
{
  "header": "Requirements",
  "bindings": "task.$item",
  "width": 170,
  "serverRender": "<ul style='margin-block-start: -16px;margin-block-end: -16px;padding-inline-start: 16px;'>#foreach($l in $item.fields().linkedWorkItems().back()) #set($r = $l.fields().workItem().get()) #set($t = $r.fields().type().get().id()) #if($t.equals(\"requirement\")) <li>$r.render().withTitle().withIcon(false).withLinks().htmlFor().forFrame() ($r.fields().description().render().htmlFor().forFrame())</li> #end #end</ul>"
}
This renders a bulleted list of all linked requirements directly in the column, with the nested risksheet link still available for full editing.
Server-rendered columns provide quick visibility into nested relationships without navigating away. Combine this with linkToRisksheet to offer both overview and drill-down capabilities.

​
Verification

  1. Save your main risksheet configuration
  2. Locate a row with downstream items configured for nested linking
  3. Click the link icon next to the downstream item name
  4. The nested risksheet should open in the same tab, showing the selected item as a row with its children visible as downstream items
  5. Edit the nested items as needed
  6. Use browser back or navigate to your main risksheet to return
You should now see a clickable link icon on downstream items that opens the nested risksheet view, allowing you to edit complex multi-level relationships without losing your place in the main risk analysis.

​
See Also

KB ArticlesSupport TicketsSource Code
  • risksheet.json
  • RisksheetProjectProperties.java
  • AppConfig.ts
  • OpenHelpCommand.ts
  • RisksheetProduct.java