This article explains how to configure downstream traceability columns for risk control measures in Risksheet. It covers how to define the structure of tasks linked to risk items, with an emphasis on the configuration file and the various options available for loading and creating new items.
By default, the mitigations section shows the tasks linked to the risk items.
TABLE OF CONTENTS
Configuration
The downstream objects are defined in the "dataTypes" section:
Then have one column that defines "taskLink" (if the Item is named differently, adjust the term instead of using task)
The ID of this column is important, as you will refer to it when adding more columns:
You see above that the bindings use the dot notation to refer to properties of the Task Work Item, where "task" is the id of the taskLink column ID.
Where to load data from?
You can use any combination of query, project, and document to load the items. It is not required to use all three options.
Starting with version 23.7.0, you may even load the items from multiple projects.
Where to create new items?
Create a new object in the current document
- By default, the new items are created in the same place where they are loaded from (see above).
- You can force the system to create new items in the current "Risksheet" document using "createInCurrentDocument":true
Creating items with multiple projects
- Starting with version 25.3.1, we improved type column handling for cross-project configurations
- The 'type' column now consistently displays the Work Item type name, even in cross-project
configurations where type pickers aggregate types from multiple projects - You may choose which project to put the task in and which type of new item will be created in Risksheet
- If you don't choose an option, the first project and type in the list will be selected by default.
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