Risksheet allows you to tailor which columns are displayed, enabling teams to focus on the most relevant information for their risk analysis workflow. Whether you’re customizing the view per document or template, the column configuration is defined in the risksheet.json file.
TABLE OF CONTENTS
- Configuration file
- Add Risk Item Column
- Add up-stream Traceability Column
- Add down-stream Traceability Column
Configuration file
The columns are defined in the risksheet.json configuration file. You can specify them per document (each document can have different columns) or per template.
Please check this article to learn where the configuration file is located Adjusting Risksheet configuration
Add Risk Item Column
Suppose you downloaded the config file, and you want to add a column pointing to a custom field.
The minimal configuration will be as shown below.
columns: [ { "headerGroup":"Potential risks", "header": "Causes(s)", "bindings": "causes", "level": 2 } ],
- "bindings": "causes" - point to the ID of the custom field, in this case, "causes"
- "level": 2 - controls that the field shall be merged according to level 2 - see What Work Items are visible on the Risksheet
Check the article Column Reference - in Risksheet Document Config File - risksheet.json for a reference of all the supported properties and their meaning.
Add up-stream traceability column
By default, Risksheet shows in the first column the up-stream traceability item, i.e., an item pointing from a risk item to a function/component. More information on how to configure up-stream traceability columns can be found here.
Add down-stream traceability column
By default, Risksheet displays level 3 items as the children of the Risk item—typically, these are mitigation tasks. More information on how to configure down-stream traceability columns can be found here.
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