Skip to main content

​
Enable Branching Support

  1. Navigate to Administration > Configuration Properties
  2. Add the following property (case-sensitive):
nextedy.risksheet.branchingSupport=true
The property name must be exactly branchingSupport (camelCase). Using BranchingSupport or other variations will cause the feature to fail silently, leaving branched documents empty or showing only reference-copied items.
  1. Save the configuration
  2. Restart Polarion or reload the RISKSHEET widget

​
Enable Editing of Referenced Work Items

By default, referenced work items in branched documents are read-only. To allow editing: 
nextedy.risksheet.editableReferencedWorkItems=true
This allows users to modify work items that exist in the original document from within the branched view.

​
Freeze Downstream Items at Revision Snapshot

By default, downstream items (mitigation tasks, controls) always reflect their latest version even in branched documents. To lock them to the state at the time of branching: 
nextedy.risksheet.downstreamFromRevision=true
This ensures audit compliance by preventing downstream items from changing after the baseline is created.

​
How Branching Works

diagram

​
Visual Comparison Indicators

When comparing a branched document to another revision, RISKSHEET uses color coding:
ColorMeaning
YellowCell value changed between revisions
GreenRow added in newer revision
RedRow removed in newer revision
GrayItem not compared (outside comparison scope)
Access comparison mode via Menu > History > Compare with…

​
Known Limitations

RISKSHEET does not currently support Polarion collections for filtering work items by release or variant in branched documents. Use the branching strategy itself as the primary scoping mechanism. For multi-release scenarios, consider creating separate branches per release.
Baselines provide read-only historical snapshots. Branching creates editable copies. Use baselines for audits and comparisons, branching for variant development or “what-if” analysis.

​
Verify the Configuration

  1. Create a baseline or branch of a RISKSHEET document in Polarion
  2. Open the branched document in RISKSHEET
  3. You should now see all work items from the original document
  4. If editableReferencedWorkItems=true, you can edit the items
  5. If downstreamFromRevision=true, downstream tasks reflect their state at the time of branching

​
See Also

KB ArticlesSupport TicketsSource Code
  • RisksheetProjectProperties.java
  • AppConfig.ts
  • AppConfigParser.ts
  • WorkItemBasedReview.java