When a downstream item on your Risksheet (e.g., a task, mitigation plan, or issue) is linked to multiple sub-items, it’s often critical to display all related components clearly within a single sheet. This helps maintain full visibility over nested or dependent work.
TABLE OF CONTENTS
Configuration
1. Create a new Risksheet configuration, where our Risk Control item is shown as the main Risk row item, and Requirements are shown as a downstream item
2. In the "dataTypes" section of the current project, add the following parameter for the "task"
"linkToRisksheet":true
3. Add the reference to the newly created document, so that at the end the whole configuration looks similar to the one below
... "task": { "type": "riskControl", "role": "mitigates", "name": "Risk Mit. Measure", "zoomColumn": "taskTitle", "document":"Risks/Mitigations", "linkToRisksheet":true } ...
4. Add a column with a "serverRender" functionality to render requirements linked to the Task items
... { "headerGroup": "Risk Control", "headerGroupCss":"headMitigations", "headerCss":"headMitigations", "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>" }, ...
5. Once you need to link some Requirements to the Risk Control item, now by clicking on it on the main Risksheet the following 'Mitigations' document will open and you will link Requirements as usual
After that, these items will be shown in the server-rendered column 'Requirements' on the main Risksheet.
For any assistance, please don’t hesitate to reach out by submitting a ticket here.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article