Skip to main content

​
Configuration Steps

​
1. Define Multiple Downstream Types

In the dataTypes section of your risksheet.json, specify multiple work item types as a comma-separated list in the type property: 
"dataTypes": {
  "risk": {
    "type": "risk"
  },
  "task": {
    "type": "task,issue,action",
    "role": "mitigates",
    "name": "Mitigation",
    "zoomColumn": "taskTitle"
  }
}
This configuration allows risks to be mitigated by Tasks, Issues, or Actions interchangeably. Add a column with "type": "taskLink" to display the link to downstream items: 
{
  "headerGroup": "Mitigations",
  "headerGroupCss": "headMitigations",
  "headerCss": "headMitigations",
  "header": "Mitigation ID",
  "type": "taskLink",
  "id": "task"
}

​
3. Add Type Display Column

Create a column to show which type each downstream item is: 
{
  "headerGroup": "Mitigations",
  "headerGroupCss": "headMitigations",
  "headerCss": "headMitigations",
  "header": "Type",
  "bindings": "task.type",
  "readOnly": true,
  "minWidth": 100
}
The work item type can be selected during creation but cannot be changed afterward. Always set "readOnly": true for type columns.

​
4. Add Downstream Item Properties

Display properties from the linked items using dot notation: 
{
  "headerGroup": "Mitigations",
  "headerGroupCss": "headMitigations",
  "headerCss": "headMitigations",
  "header": "Title",
  "bindings": "task.title",
  "id": "taskTitle",
  "minWidth": 200
},
{
  "headerGroup": "Mitigations",
  "headerGroupCss": "headMitigations",
  "headerCss": "headMitigations",
  "header": "Status",
  "bindings": "task.status",
  "minWidth": 120
}

​
Configuration Flow

diagram

​
Type-Specific Custom Fields

You can display custom fields that exist only for specific work item types. If a field doesn’t exist for a particular type, RISKSHEET stores the value in a generic string field. 
{
  "headerGroup": "Mitigations",
  "headerGroupCss": "headMitigations",
  "headerCss": "headMitigations",
  "header": "Priority",
  "bindings": "task.customPriority",
  "minWidth": 100
}
Starting with version 25.2.1, multiEnum fields are properly handled for type-specific custom fields. If you experience linking issues with multiEnum fields, update to this version or newer.

​
Multi-Project Configuration

When loading downstream items from multiple projects (available since 23.7.0), add project and type columns: 
{
  "headerGroup": "Mitigations",
  "headerGroupCss": "headMitigations",
  "headerCss": "headMitigations",
  "header": "Project",
  "bindings": "task.project",
  "readOnly": true,
  "minWidth": 120
}
Specify multiple projects in the dataTypes configuration: 
"task": {
  "type": "task,issue",
  "role": "mitigates",
  "name": "Mitigation",
  "zoomColumn": "taskTitle",
  "projects": "ProjectA,ProjectB"
}
If you don’t explicitly select a project and type when creating items, the first project and first type in your comma-separated lists will be used by default.

​
Verification

After configuration, verify the setup:
  1. Open your RISKSHEET document
  2. Create a new mitigation item for a risk
  3. Check: Type picker dropdown shows all configured types (Task, Issue, Action)
  4. Select a type and create the item
  5. Check: Type column displays the selected work item type
  6. Check: Item properties (title, status, custom fields) appear correctly
  7. Check: Type column remains read-only after creation
You should now see a flexible mitigation tracking system where each risk can be addressed by different types of downstream work items based on your project workflow.

​
See Also