Configure Multi-Project Setup - Nextedy Documentation

Prerequisites

Risksheet installed and licensed on all participating projects
At least one working Risksheet document in your primary project
Knowledge of the project IDs for each Polarion project you want to connect
Permissions to edit Risksheet configuration in each project

Understand the Multi-Project Architecture

Step 1: Configure Cross-Project Upstream Columns

To display linked work items from another project, add the project parameter to your column’s typeProperties in risksheet.json:

{
  "columns": [
    {
      "id": "upstreamRequirements",
      "label": "Requirements",
      "type": "multiItemLink",
      "typeProperties": {
        "linkRole": "relates_to",
        "project": "RequirementsProject",
        "itemType": "requirement"
      }
    }
  ]
}

The project parameter accepts the Polarion project ID (not the display name) of the source project.

The project parameter in typeProperties works for directly linked items only. If items are linked through intermediary work items in another project, those indirect links will not resolve automatically and require additional configuration.

Step 2: Configure Multiple Projects in a Single Column

To load items from several projects into one column, use Velocity snippets with $config properties in typeProperties:

{
  "typeProperties": {
    "linkRole": "relates_to",
    "project": "$config.sourceProject1 $config.sourceProject2",
    "itemType": "requirement"
  }
}

Define the corresponding configuration properties at the project level so each deployment can specify its own source projects.

When using configuration properties to define multi-project columns, empty property values after the = sign cause errors. Always ensure each property resolves to a valid project ID. Avoid referencing another configuration property variable as the alternative project value.

Step 3: Enable Cross-Project Item Creation

When a multi-project column links to items across projects, newly created items default to saving in the linked project. To create new items in the current project instead, set createInCurrentDocument:

{
  "typeProperties": {
    "linkRole": "relates_to",
    "project": "ExternalProject",
    "itemType": "task",
    "createInCurrentDocument": true
  }
}

Property	Value	Behavior
`createInCurrentDocument`	`true`	New items saved in the current project and document
`createInCurrentDocument`	`false` (default)	New items created in the source project specified by `project`

Setting createInCurrentDocument to true ensures new items are saved in the current project. Selecting a specific target project for new items (other than current or source) is not yet supported.

Step 4: Configure Cross-Project Downstream Tasks

For downstream mitigation tasks or verification activities stored in a separate project, configure the downstream column with the target project:

{
  "columns": [
    {
      "id": "mitigationTasks",
      "label": "Mitigation Tasks",
      "type": "taskLink",
      "typeProperties": {
        "project": "VerificationProject",
        "taskType": "task"
      }
    }
  ]
}

Work item deletion and unlinking across projects uses the IdProject format (project/itemId) internally. Risksheet handles this mapping automatically.

Step 5: Verify the Configuration

After saving your changes:

Open the Risksheet document in your primary project
Verify that cross-project columns load items from the expected projects
Try creating a new item in a cross-project column and confirm it saves to the correct project
Check that linked items display their project-qualified IDs when hovering

You should now see items from multiple projects rendered in your Risksheet columns.

In clustered Polarion deployments, configuration changes may not immediately propagate to all nodes. If the Risksheet displays differently across cluster nodes, refresh the page or clear the cache.

Common Multi-Project Scenarios

Scenario	Configuration Approach
FMEA with external requirements	`multiItemLink` column with `project` pointing to requirements project
Shared risk components	Cross-project linking with `project` in `typeProperties`
Verification tasks in separate project	`taskLink` column with `project` targeting the verification project
FHA loading existing functions	Upstream `multiItemLink` with `project` and `itemType` set to load Function items

Risksheet cannot auto-populate rows with existing items from another project. The sheet starts empty and requires risk items to be created first, then linked to upstream items manually.

​Prerequisites

​Understand the Multi-Project Architecture

​Step 1: Configure Cross-Project Upstream Columns

​Step 2: Configure Multiple Projects in a Single Column

​Step 3: Enable Cross-Project Item Creation

​Step 4: Configure Cross-Project Downstream Tasks

​Step 5: Verify the Configuration

​Common Multi-Project Scenarios

​See Also

Prerequisites

Understand the Multi-Project Architecture

Step 1: Configure Cross-Project Upstream Columns

Step 2: Configure Multiple Projects in a Single Column

Step 3: Enable Cross-Project Item Creation

Step 4: Configure Cross-Project Downstream Tasks

Step 5: Verify the Configuration

Common Multi-Project Scenarios

See Also