Use Case
Variant management enables teams managing multiple product configurations or releases to:- Filter Risksheet views to show only risks relevant to a specific release
- Link mitigation tasks to the correct product variant
- Maintain separate risk matrices for different configurations while sharing common work items
Configure Release Field
First, create a custom field in Polarion to track which releases apply to each work item.Create Multi-Enum Field
- Navigate to Administration > Work Items > Custom Fields
- Create a new custom field:
- Field ID:
assignedReleases - Field Type: Multi-Enum
- Allowed Values:
Release_1.0,Release_2.0,Release_3.0, etc.
- Field ID:
- Apply the field to relevant work item types (Risk, Mitigation, etc.)
Add Release Column to Risksheet
Add the release field to yourrisksheet.json:
Filter by Target Release
Currently, Nextedy RISKSHEET does not support automatic release-based filtering at the widget level. The workaround is to use branched documents or query-based scoping.Option 1: Branched Documents (Recommended)
Use Polarion’s document branching to create release-specific Risksheet documents:- Create a baseline for each release (e.g.,
v1.0-baseline) - Branch your Risksheet document from that baseline
- Each branched document automatically contains only the work items from that release snapshot
Option 2: Query Configuration
Use thequery property in risksheet.json to filter work items by release:
Release_2.0.
Known Limitations
| Limitation | Impact | Workaround |
|---|---|---|
| No widget-level release filtering | Cannot filter matrix by target release when document spans multiple releases | Use branched documents or query filtering |
| Hardcoded multiEnum support | Release filtering only works with multiEnum fields | Ensure assignedReleases is configured as multiEnum type |
| Cross-release link visibility | Linked items from other releases may appear in link columns | Use conditional rendering in serverRender columns to hide mismatched releases |
Advanced: Conditional Link Rendering
Filter linked items to show only those matching the current release:- Sets
$targetReleaseto the desired release version - Loops through linked work items
- Checks if
assignedReleasescontains the target release - Renders only matching items
Verification
- Open your Risksheet document
- You should see the Assigned Releases column showing multi-select enum values
- If using query filtering, verify that only work items matching the query appear
- If using branched documents, verify that the branch contains only items from the baseline snapshot
See Also
- Branched Documents - Recommended approach for release-based variant management
- Query Configuration - Advanced query filtering techniques
- Multi-Enum Columns - Configuring multi-select enumeration fields
- URL Parameters - Dynamic filtering via URL parameters
- Conditional Linking - Control which items appear in link columns
Sources
Sources
Support TicketsSource Code
RisksheetProjectProperties.javaAppConfigParser.tsPolarionAppConfigManager.javaRisksheetViewServlet.javaAppConfig.ts