Skip to main content

​
Add the Project Parameter

Add the project property to your itemLink or multiItemLink column’s typeProperties section: 
{
  "columns": [
    {
      "header": "System Requirement",
      "type": "itemLink",
      "width": 200,
      "typeProperties": {
        "linkRole": "verifies",
        "linkTypes": "requirement",
        "project": "system_library"
      }
    }
  ]
}
This configuration loads requirements from the system_library project instead of the current project.
Reference configuration properties using Velocity syntax: "project": "$config.sharedProjectId" to avoid hardcoding project IDs.

​
Configure Multi-Project Sources

To pull items from multiple projects, use space-separated Velocity snippets: 
{
  "header": "Linked Components",
  "type": "multiItemLink",
  "typeProperties": {
    "linkRole": "depends_on",
    "linkTypes": "component",
    "project": "$config.primaryProject $config.secondaryProject fallback_project"
  }
}
Fallback projects must use hardcoded project IDs, not configuration property variables. Empty configuration property values will cause errors.

​
Cross-Project Linking Limitations

The project parameter works only for direct links—it cannot traverse multi-hop dependencies: What works:
  • Risk in Project A links directly to Harm in Project B
  • Specifying "project": "project_b" retrieves the Harm
What doesn’t work:
  • Risk in Project A links to Harm in Project A, which links to Requirement in Project B
  • The project parameter cannot retrieve transitive dependencies across project boundaries
diagram

​
Option 1: Nested Risksheets

Create separate Risksheets for each project and link them:
  • Project A Risksheet shows Risks → Harms
  • Project A Harm detail page embeds Project B Risksheet showing Harms → Requirements
See Open Nested Risksheets for implementation.

​
Option 2: Data Denormalization

Add custom fields to duplicate critical cross-project data:
  • Add a “Linked Requirement” field to the Harm work item type
  • Populate this field manually or via workflow automation
  • Reference the denormalized field directly in Project A Risksheet

​
Option 3: Branched Documents

Use Polarion’s branching feature to reference work items across projects within a single document context. See Work with Branched Documents.

​
Configure Cross-Project Item Creation

Control where new linked items are created using the createInDocument property: 
{
  "typeProperties": {
    "linkRole": "verifies",
    "linkTypes": "requirement",
    "project": "system_library",
    "createInDocument": "Requirements/System"
  }
}
New requirements created from the autocomplete dropdown will be stored in the Requirements/System document within the system_library project.
The createInDocument property requires RISKSHEET version 24.8.1 or later.

​
Verification

  1. Open your Risksheet document
  2. Click the autocomplete dropdown in your cross-project column
  3. Type at least 3 characters to trigger search
  4. ✅ You should see work items from the specified project(s) in the results
  5. Select an item to create a cross-project link
  6. Verify the linked item’s project badge shows the correct project ID

​
See Also

KB ArticlesSupport TicketsSource Code
  • RisksheetDataStorage.java
  • AppConfig.ts
  • WorkItemBasedReview.java
  • DefaultTraceProvider.java
  • AppConfigParser.ts