This article explains how to configure downstream traceability columns for tasks 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
First, define the work item type for the task in the "dataTypes" section.
In this example, the downstream object will be work items with the WI type ID riskControl.
"dataTypes": {
"risk": {
"type": "risk"
},
"task": {
"type": "riskControl",
"role": "mitigates",
"name": "Risk Mit. Measure",
"zoomColumn": "taskTitle"
}
}, Add a column that will show the link to the downstream object on Risksheet.
Add "type": "taskLink" to the configuration.
{
"headerGroup": "Risk Control",
"headerGroupCss": "headMitigations",
"headerCss": "headMitigations",
"header": "RC ID",
"type": "taskLink",
"id": "task"
}, The "id" of this column is important, as you will refer to it when adding more columns.
For example, if you want to show the title of the work item in a column.
{
"headerGroup": "Risk Control",
"headerGroupCss": "headMitigations",
"headerCss": "headMitigations",
"header": "Risk Control",
"bindings": "task.title",
"id": "taskTitle",
"minWidth": 170
}, 
The bindings for these columns use the dot notation to refer to properties of the "task" work item, where "task" is the "id" of the taskLink column ID (as seen in the previous step).
This means that if the "id": "issue", then the "bindings" will be "issue.title". If you want to show the status, then it would be "issue.status".
Here are a few more examples to help you understand what to put into "bindings" for the property to show on Risksheet.
| "id" of "task" column | Property of "task" item | "bindings": |
| task | title | "task.title" |
| task | status | "task.status" |
| issue | title | "issue.title" |
| issue | status | "issue.status" |
| requirement | dueDate | "requirement.dueDate" |
Where to load data from?
Document/Project/Query
You can use any combination of query, project, and document to load the items. It is not required to use all three options.
You must use the full document path to use the document parameter.
In this example "Risks" is the folder name and "harms" is the name of the document.
....
"task": {
....
"document":"Risks/harms",
"project":"med_library",
"query":"status:released"
}
... Starting with version 23.7.0, you may even load the items from multiple projects.
...
"task": {
...
"projects":"RiskFMEA,TestRisk1" 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
...
"task": {
"type": "task",
"role": "mitigates",
"name": "Task",
"zoomColumn": "taskTitle",
"createInCurrentDocument": true
}Create a new object in any document
- Starting with version 24.8.1, you can specify a target document for new items with the flexibility to load items from any location
- Use the property "createInDocument": "document path"
...
"task": {
"type": "task",
"role": "mitigates",
"name": "Task",
"zoomColumn": "taskTitle",
"createInDocument":"Risks/Tasks"
}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.
....
{
"headerGroup": "Mitigations",
"headerGroupCss": "headMitigations",
"headerCss": "headMitigations",
"header": "Task title",
"bindings": "task.title",
"id": "taskTitle",
"collapseTo": true,
"minWidth": 170
},
{
"headerGroup": "Mitigations",
"headerGroupCss": "headMitigations",
"headerCss": "headMitigations",
"header": "Task project",
"bindings": "task.project",
"readOnly":true,
"minWidth": 170
},
{
"headerGroup": "Mitigations",
"headerGroupCss": "headMitigations",
"headerCss": "headMitigations",
"header": "Type",
"bindings": "task.type",
"readOnly": true,
"minWidth": 170
},Separate the projects with a comma in "project":
...
"task": {
"type": "task,issue,customTypeTestID",
"role": "mitigates",
"name": "Task",
"zoomColumn": "taskTitle",
"project": "RiskFMEA,TestRisk1"
}
...Additional Configurations
Check the following articles to learn about more flexible configurations.
Click on the title to open the full article in a new tab.Multiple Downstream Work Item Types
In many projects, managing risks involves more than one type of downstream work item. For example, a Risk might be mitigated by either a Task or an Issue, depending on the situation. Risksheet supports this flexibility by allowing you to configure and display multiple downstream Work Item (WI) types within a single Risksheet.
This feature helps you reflect real-world workflows more accurately, as not all mitigations are strictly “Tasks”—some may naturally fall under the “Issue” category. It also improves visibility into how risks are being addressed, regardless of the specific item type, and allows you to take advantage of type-specific custom fields for better reporting and decision-making. By consolidating these item types in one place, you avoid fragmenting your data across different documents or configurations, resulting in a more cohesive and efficient risk management process.
Show ID and Title in one column for Downstream items
By default, Risksheet displays the Title and ID of downstream work items in separate columns, which aligns with Risksheet's standard behavior. However, in certain cases—such as when screen space is limited or for improved readability—it may be more convenient to combine both fields into a single column.
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