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.

TABLE OF CONTENTS

• Configuration
  • Define multiple types
  • Add a column to display the work item type
• Type-specific custom fields

Configuration

Define multiple types

To support more than one downstream type (e.g., both Task and Issue), update the "dataTypes" section using a comma-separated list in the "type" property.

  "dataTypes": {
    "risk": {
      "type": "risk"
    },
    "task": {
      "type": "task,issue",
      "role": "mitigates",
      "name": "Task",
      "zoomColumn": "taskTitle"
    }
  },

      {
        "headerGroup":"Mitigations",
        "headerGroupCss":"headMitigations",
        "headerCss":"headMitigations",
        "header": "Type",
        "bindings": "task.type",
        "readOnly":true,
        "minWidth": 170		
      },

Note: Set the column to "readOnly": true
    • You can still select the WI type when creating new items
    • However, once created, the WI type cannot be changed

Note: There was an issue with handling multiEnum field if it was defined for a specific work item type only. This issue was resolved in Risksheet version 25.2.1.
If you have issues with linking items that do not have multiEnum field, make sure to update the Risksheet to that version or newer.