Binding Path Syntax Binding paths specify which work item fields appear in columns. The binding syntax varies by work item type and hierarchy level.
Binding Pattern Type Description Example fieldIdMaster field Direct field access on risk item title, description, customField1task.fieldIdTask-level field Field access on linked mitigation task task.title, task.statustask.link.roleTask link role Name of the link relationship between risk and task task.link.mitigatestask.assigneeTask assignee User assigned to the mitigation task task.assigneeupstream.fieldIdUpstream link Field from upstream-linked work item upstream.requirementdownstream.fieldIdDownstream link Field from downstream-linked work item downstream.issue
Master-Level Field Access Master-level bindings access fields directly on the risk item without any prefix.
Field Category Binding Data Type Read-Only Notes Identifiers idString Yes Unique work item identifier Identifiers keyString Yes Deprecated; use id Content titleString No Work item title/summary Content descriptionText No Rich text description field Content longDescriptionText No Extended description field Status statusEnum No Current workflow status Status resolutionEnum Yes Resolution enumeration Status typeEnum Yes Work item type (risk, task, issue, etc.) Metadata authorUser Yes User who created the item Metadata createdDateTime Yes Creation timestamp Metadata updatedDateTime Yes Last modification timestamp Metadata obsoleteBoolean No Marks item as obsolete/archived Custom customField[N]Variable No Custom project fields (1-indexed)
Task-Level Field Access Task-level bindings require the task. prefix and access fields on linked mitigation items.
Binding Data Type Description Configuration task.idString Identifier of the linked task Read-only task.titleString Title of the linked task Editable task.statusEnum Current status of the task Editable task.typeEnum Work item type of the task Read-only after creation task.assigneeUser User assigned to the task Editable task.priorityEnum Priority level of the task Editable task.dueDateDate Due date for task completion Editable task.effortInt Estimated effort in work units Editable
Upstream and Downstream Field Access Upstream bindings reference fields on work items that link TO the current risk. Downstream bindings reference fields on work items that the risk links TO.
Upstream Pattern Used for traceability columns showing requirements or parent items.
Binding Meaning Example upstream.idID of upstream-linked item View requirement identifier upstream.titleTitle of upstream-linked item Show requirement title upstream.statusStatus of upstream item Display requirement status
Downstream Pattern Used for traceability columns showing derived tasks or test cases.
Binding Meaning Example downstream.idID of downstream-linked item View verification task downstream.titleTitle of downstream item Show test case name downstream.resultCustom field on downstream item Display test result
Hierarchical Level Binding RISKSHEET supports multi-level hierarchies where different columns appear at different levels.
{ "level" : 1 , "bindings" : "title" }
Property Type Default Purpose levelNumber 1 Which hierarchy level (1=top, 2=sub-item, etc.) bindingsString None Field binding path for this level
Field Type Inference When no explicit type is specified, RISKSHEET infers the column type from the Polarion field definition.
Polarion Field Type RISKSHEET Column Type Text textTextMultiLine text (multiLine: true)Enumeration enum:enumIdReference ref:refIdDate dateDateTime datetimeInteger intFloating Point floatBoolean boolean
Binding Validation Binding paths are validated at load time. Invalid bindings result in configuration warnings.
Valid Binding Examples { "header" : "Risk Title" , "bindings" : "title" , "type" : "text" }
{ "header" : "Mitigation Status" , "bindings" : "task.status" , "type" : "enum:workflowStatus" }
{ "header" : "Requirement" , "bindings" : "upstream.title" , "readOnly" : true }
Multi-Binding Columns Some column types support multiple bindings to display data from different sources.
Column Type Binding Pattern Purpose Multi-Enum field1,field2Combine multiple enum fields Consolidated Link upstream.id|downstream.idShow both upstream and downstream links Calculated field1+field2Formula-based calculation
System Field Binding System fields are read-only Polarion fields that cannot be modified through RISKSHEET.
Bindings to author, created, updated, type, and resolution create read-only columns. These fields are protected by Polarion and cannot be edited through the grid interface.
{ "header" : "Created By" , "bindings" : "author" , "readOnly" : true }
Binding Path Resolution Flow Binding Prefix Matching When configuring dependent enumerations or relationship rules, binding prefixes must match. Master fields cannot have relationships with task fields.
Relationship mappings require both ‘from’ and ‘to’ columns to use the same binding prefix (both master-level or both task-level). Cross-level relationships are not supported.
Valid Relationship Invalid Relationship Reason category → type (both master)category → task.typeDifferent levels task.priority → task.effort (both task)priority → task.effortMixed levels
Reference to Available Pages For detailed information about specific field types and how they behave in columns, see:
Source Code
AppConfigParser.tsRelationActionController.tsAppConfigHelper.ts 
