Skip to main content

​
Basic Configuration

The upstream/parent column uses the itemLink column type to connect Risk items to their upstream dependencies. Minimum required configuration: 
{
  "headerGroup": "Potential risks",
  "header": "Item/Func",
  "type": "itemLink",
  "width": 150,
  "filterable": true,
  "level": 1,
  "typeProperties": {
    "linkRole": "assesses",
    "linkTypes": "systemrequirement,softwarerequirement"
  }
}
Key properties:
  • "type": "itemLink" — Declares this column displays linked work items
  • "linkRole" — The Polarion link role connecting the Risk item to its parent (e.g., “assesses”, “assessedHazard”)
  • "linkTypes" — Comma-separated list of allowed work item types (e.g., “systemrequirement,softwarerequirement,systemelement”)
  • "level": 1 — Indicates this is a top-level upstream column

​
Upstream Traceability Flow

diagram

​
Loading Upstream Items

​
Filter by Document, Project, or Query

You can use any combination of document, project, and query to control which upstream items are available for linking: 
"typeProperties": {
  "linkRole": "assessedHarm",
  "linkTypes": "harm",
  "document": "Risks/harms",
  "project": "med_library",
  "query": "status:released"
}
Use the full document path: "FolderName/DocumentName". For example, if your harms are stored in the “Risks” folder in a document called “harms”, use "document": "Risks/harms".

​
Dynamic Query Filtering with Query Factory

Use queryFactory to filter upstream items based on other column values. For example, load situations that are linked to a specific event: 
{
  "queryFactories": {
    "situationsQuery": "function(info){return 'linkedWorkItems:'+info.item['assessedSequence']}"
  },
  "columns": [
    {
      "header": "Hazardous Situation",
      "type": "itemLink",
      "level": 3,
      "id": "assessedHazardousSituation",
      "bindings": "assessedHazardousSituation.description",
      "typeProperties": {
        "linkRole": "assessedHazardousSituation",
        "linkTypes": "hazardousSituation",
        "queryFactory": "situationsQuery",
        "createInCurrentDocument": true,
        "document": "Risks/hazardSituations"
      }
    }
  ]
}
⚠️ The project parameter in typeProperties only filters direct links — not transitive multi-hop links across projects. If Risk in Project A links to Harm in Project A, which then links to Requirement in Project B, the upstream column cannot retrieve the transitive dependency.

​
Creating New Upstream Items

​
Disable “Create New” Option

By default, RISKSHEET suggests creating a new upstream item if none exists. To disable this: 
{
  "header": "Harm",
  "type": "itemLink",
  "canCreate": false,
  "typeProperties": {
    "linkRole": "assessedHarm",
    "linkTypes": "harm"
  }
}

​
Create in Current Document

Force new items to be created in the current Risksheet document: 
"typeProperties": {
  "linkRole": "assessedHazardousSituation",
  "linkTypes": "hazardousSituation",
  "createInCurrentDocument": true,
  "document": "Risks/hazardSituations"
}

​
Create in Specific Document

Starting with version 24.8.1, specify a target document for new items while loading from a different location: 
"typeProperties": {
  "linkRole": "assessedHazardousSituation",
  "linkTypes": "hazardousSituation",
  "project": "med_library",
  "createInDocument": "Risks/hazardSituations"
}
You can also display backlinks (reverse relationships) as upstream columns. Set "backLink": true in typeProperties: 
{
  "header": "Causes",
  "type": "multiItemLink",
  "level": 2,
  "id": "causes",
  "canCreate": true,
  "typeProperties": {
    "linkRole": "effect",
    "linkTypes": "risk",
    "backLink": true,
    "createInCurrentDocument": true
  }
}
This displays work items that link to the current Risk item via the “effect” link role, rather than items the Risk links to.

​
Adding Sub-Columns

Once you configure an upstream itemLink column, you can display properties of the linked item using dot notation in the bindings property: 
{
  "header": "Harm Severity",
  "bindings": "assessedHarm.harmSeverity",
  "type": "enum:harm_severity_5",
  "readOnly": true,
  "level": 3
}
By default, sub-columns showing upstream item properties are read-only to prevent unintended changes to shared upstream objects. You can override this with "readOnly": false, but users may not realize changes impact other Risksheets.

​
Verification

After configuring upstream traceability columns:
  1. Open your Risksheet in Polarion
  2. The upstream column should appear with a clickable link icon
  3. Click the cell to open the item picker showing filtered upstream items
  4. Select an upstream item to create the link
  5. Sub-columns should populate with properties from the linked item

​
See Also