Configure Multiple Risk Item types

Starting with version 23.7.7, Risksheet introduces support for multiple Risk (row) Work Item types, giving you greater flexibility when managing various kinds of risk-related items in your project. Previously limited to a single type, you can now define a selection of allowed types and choose the appropriate one from a dropdown when creating a new Risk item.

TABLE OF CONTENTS

• Multiple Risk Work Item types configuration
  • Specify Risk Work Item types
  • Create a specific column that shows the type
• Multiple Link Roles for Item Link columns configuration

Multiple Risk Work Item types configuration

Specify Risk Work Item types

In the "dataTypes" section of the Risksheet configuration, put comma-separated IDs of Work Item types that will correspond to the Risk level.

...
"dataTypes": {
    "risk": {
      "type": "risk,issue"
    },
...

Create a specific column that shows the type

When creating a new Risk item, you will be able to specify from the dropdown menu what WI type it should be created as (see the image in the introduction).

...
{
      "headerGroup": "Potential Failure",
      "headerGroupCss": "headPotentialRisks",
      "headerCss": "headPotentialRisks",
      "header": "Item Type",
      "bindings": "type",
      "minWidth": 150,
      "id": "itemType",
      "level": 2
    },
...

Note: When the item is already created, it is no longer possible to change its type in Risksheet.

Multiple Link Roles for Item Link columns configuration

In some cases, Risksheet may display multiple types of Risk-related Work Items within the same view. When this happens, you might need to use different link roles for the same upstream column, depending on the type of the Risk item in a given row.

This feature has been supported since version 24.2.2. Before using this feature, add the following property to Administration > Configuration properties to enable it first.

nextedy.risksheet.checkLinkRoleCompliance=true

...
  {
      "headerGroup": "Potential Failure",
      "headerGroupCss": "headPotentialRisks",
      "headerCss": "headPotentialRisks",
      "header": "Item/Func",
      "type": "itemLink",
      "level": 1,
      "id": "item",
      "typeProperties": {
        "linkRole": "assesses,relates",
        "linkTypes": "systemrequirement,softwarerequirement"
      }
...

...
"dataTypes": {
    "risk": {
      "type": "risk,issue"
    },
...

Note: The order of "linkRole" and "type" values matters, meaning:
    •    The first role (assesses) corresponds to the first data type (risk)
    •    The second role (relates) corresponds to the second data type (issue)