Configure Multiple Risk Types - Nextedy Documentation

Define Risk Data Types

Configure the dataTypes section in your risksheet.json to specify each risk item type. The dataTypes.risk object defines the primary risk work item type:

{
  "dataTypes": {
    "risk": {
      "type": "fmeaRisk",
      "role": "has_risk"
    }
  }
}

Property	Description	Default
`dataTypes.risk.type`	Polarion work item type for risk items	None (required)
`dataTypes.risk.role`	Link role used when creating relationships to risk items	None (required)
`dataTypes.risk.removeStrategy`	Strategy for removing risk items (`delete` or other)	`delete`

Add Additional Risk Item Types via Levels

To include multiple risk types in a single Risksheet, define separate levels entries in your configuration. Each level maps to a specific work item type and controls hierarchy and menu behavior:

{
  "dataTypes": {
    "risk": {
      "type": "hazard",
      "role": "has_risk"
    },
    "task": {
      "type": "mitigationAction",
      "role": "mitigates",
      "showInMenu": true
    }
  },
  "levels": [
    {
      "name": "Hazard",
      "type": "hazard",
      "controlColumn": "systemItemId",
      "showInMenu": true
    },
    {
      "name": "Failure Mode",
      "type": "fmeaRisk",
      "controlColumn": "riskId",
      "showInMenu": true
    }
  ]
}

The showInMenu property (default: true) controls whether the level type appears in the context menu for creating new items. Set it to false for levels that should not be created directly from the menu.

Set Project Property for Multiple Document Types

When your project contains multiple risk document types, configure the project property with the correct syntax:

nextedy.risksheet.riskDocumentType=(riskAnalysis URRA)

When specifying multiple document types in the riskDocumentType project property, you must enclose them in parentheses with space separation: (type1 type2). Omitting the parentheses causes only the first type to be recognized.

Assign Columns to Hierarchy Levels

Different risk types may need different columns. Use the level property on columns to assign them to specific hierarchy levels:

{
  "columns": [
    { "binding": "title", "header": "Title", "level": 1 },
    { "binding": "severity", "header": "S", "type": "enum:severity", "level": 2 },
    { "binding": "occurrence", "header": "O", "type": "enum:occurrence", "level": 2 },
    { "binding": "rpn", "header": "RPN", "formula": "commonRpn", "level": 2 }
  ]
}

The level property (default: 1) determines at which hierarchical level the column appears. Task columns do not use the level property.

Risksheet supports multiple configurations within a single project. Each risk document can have its own risksheet.json with independent column layouts, risk types, and rating scales. You can also store new upstream items within the same document using the createInCurrentDocument parameter.

Configure Rejection Handling Per Type

When using review workflows with multiple risk types, configure rejection behavior in the dataTypes.risk section:

{
  "dataTypes": {
    "risk": {
      "type": "fmeaRisk",
      "role": "has_risk",
      "rejectedAction": "reject",
      "rejectedStatus": "rejected",
      "rejectedResolution": "invalid"
    }
  }
}

Property	Description	Default
`rejectedAction`	Workflow action to execute when a risk item is rejected	`reject`
`rejectedStatus`	Status value to set on rejection	`rejected`
`rejectedResolution`	Resolution value to set on rejection	`invalid`

Verify Your Changes

You should now see work items of all configured types displayed in the Risksheet grid, organized by your level hierarchy. The context menu should show creation options for each type where showInMenu is true. Items with types not listed in the configuration should be automatically filtered out.

​Define Risk Data Types

​Add Additional Risk Item Types via Levels

​Set Project Property for Multiple Document Types

​Assign Columns to Hierarchy Levels

​Configure Rejection Handling Per Type

​Verify Your Changes

​See Also

Define Risk Data Types

Add Additional Risk Item Types via Levels

Set Project Property for Multiple Document Types

Assign Columns to Hierarchy Levels

Configure Rejection Handling Per Type

Verify Your Changes

See Also