Skip to main content
Risksheet does not scope its grid to a Polarion collection. Collection scoping is a capability of Nextedy POWERSHEET and is not planned for Risksheet. To scope risk analysis by release in Risksheet, use document branching, described below.

​
How Risksheet Behaves in a Collection

Risksheet displays all work items belonging to a LiveDoc document regardless of Polarion collection context. When you open a Risksheet document within a collection, the grid shows the complete set of risk items rather than filtering to only those items relevant to the selected collection or revision. This means that enterprise workflows relying on Polarion collections for release management will not see collection-scoped views in Risksheet. Scope each release with a branched document instead.

​
Scope Risk Analysis by Release with Branching

Document branching is the supported way to manage risk analysis per release in Risksheet. Each branched document holds the risk items of one release at the correct revision.
1

Enable Branching Support

Set the project administration property nextedy.risksheet.branchingSupport=true. The property name is case-sensitive: use a lowercase n in nextedy, or branching features will not appear.
2

Branch Your Risk Documents for Each Release

Branch your risk documents for each release. Each branched document maintains its own set of risk items at the correct revision.
See Work with Branched Documents for detailed setup instructions.
Why Branching Covers Release ScopingDocument branching provides revision-specific views, release scoping, and isolated editing for each release. This is the recommended approach for release management in Risksheet.

​
Restrict Linked Items to a Release Document

If you keep one document per release without branching, you can also restrict which linked items each Risksheet document loads.

​
Organize Risk Documents by Release

Structure your risk analysis documents so that each document corresponds to a specific release or product scope:
  1. Create separate LiveDoc documents for each release milestone
  2. Keep risk items scoped to the document they belong to
  3. Use the document property in dataTypes to restrict linked item loading to a specific document
This configuration ensures that only mitigation tasks from the specified document appear in the Risksheet grid, effectively scoping your view to a single release.

​
Create a Saved View

  1. Configure column visibility for the desired scope
  2. Save the view with a descriptive name (e.g., “Release 2.0 View”)
  3. Share the view name with team members for consistent access
For details on creating saved views, see Create Saved Views.

​
Read-Only Mode in Historical Revisions

When viewing Risksheet documents at a historical revision (whether through a collection or direct URL), Risksheet automatically enters read-only mode. The readonly property is forced to true when a non-empty revision value is set, preventing any edits to historical data. This behavior applies to:
  • Documents opened via collection at a specific revision
  • Documents accessed with a revision URL parameter
  • Baseline snapshots of risk analysis documents
No Editing in Historical RevisionsYou cannot modify risk items when viewing a historical revision. If you need to edit items from a past release, work in the current (HEAD) revision of the branched document instead.

​
Collection-Scoped Sheets in Powersheet

A sheet that shows only the work items of a collection’s documents, each at the revision the collection pins, is a Powersheet capability. See Collection-Scoped Sheets for how it works, and Powersheet vs. Risksheet for how the two products differ.

​
Verification

After setting up release scoping:
  1. Open the branched Risksheet document for a release
  2. You should now see only the risk items of that release
  3. Verify that saved views show the columns you expect
  4. Confirm that historical revisions open in read-only mode

​
See Also