Skip to main content

Symptoms

  • The baseline list shows “Loading” and never completes
  • Baselines fail to load after selecting them from Menu > Document > Show Baselines
  • Comparison mode displays incorrect or missing data
  • PDF exports show incorrect or missing baselines
  • Baseline option is not visible in the menu

Check Baseline Availability

Baseline comparison is available from Risksheet version 24.2.0. If baselines do not appear:
  1. Verify your Risksheet version is 24.2.0 or later
  2. Access baselines via Menu > Document > Show Baselines
  3. Confirm that at least one document baseline exists for the current document
diagram

Enable Project Baselines

By default, only document baselines are shown. To include project baselines, set the following property in Administration > Configuration Properties:
nextedy.risksheet.includeProjectBaselines=true
Project baselines are disabled by default. Enable them via nextedy.risksheet.includeProjectBaselines=true in Administration Configuration Properties if you need to compare against project-level baselines.

Fix Baselines Stuck on “Loading”

When baselines display “Loading” indefinitely, the issue is typically a server-side error.
  1. Check the Polarion server logs for errors related to baseline loading
  2. Verify the user has sufficient permissions to read document baselines
  3. Confirm the document is not in a corrupted state
Baselines stuck on “Loading” indicate a server-side problem rather than a client-side issue. Check Polarion server logs for the specific error message before attempting client-side troubleshooting.

Fix Baseline Comparison Display Issues

When comparing to a baseline, the grid highlights three types of changes:
Change TypeVisual IndicatorDescription
Added itemsRow highlight (new)Risk items added since the baseline
Removed itemsGhost rowsItems that existed in the baseline but are now removed
Modified itemsCell-level highlightIndividual properties that changed between revisions
Ghost rows are temporary visual placeholders for items that were removed since the baseline. They appear in the grid during comparison but are not saved back to Polarion. If comparison results appear incorrect:
  1. Save all pending changes before starting the comparison — unsaved changes interfere with diff calculation
  2. Exit comparison mode using the cancel option, then re-enter by selecting the baseline again
  3. Use the Show Unchanged toggle to filter the view to only changed items, making it easier to identify differences
Hover over highlighted cells during comparison to see tooltips explaining what changed. The tooltip shows the specific property name and the before/after values for that cell.

Fix PDF Export Baseline Issues

PDF exports may display incorrect or missing baselines, particularly in variant projects.
PDF export baseline display may show incorrect or missing baselines when using variant projects. Baselines should be identified by document ID/path for reliability. Exit comparison mode before generating a PDF export.

Create a New Baseline

If you need to create a baseline for future comparison:
  1. Ensure the document has no unsaved changes
  2. Use the baseline creation option from the Risksheet menu
  3. Enter a descriptive baseline name (e.g., version number or milestone name)
  4. The baseline captures a point-in-time snapshot of the current document state
Baseline names cannot be empty. Whitespace is automatically trimmed. Special characters are supported and URL-encoded automatically. If you cancel the prompt or enter an empty name, you see the message “Action canceled. Please provide a baseline name.” After successful creation, the newly created baseline appears immediately in the baseline selection list without requiring a page reload.
Use descriptive names like version numbers (v2.1), milestone names (Design Review), or dates (2024-Q3 Release). This makes it easier to identify the correct baseline when comparing later.

Fix Baselines in Variant Projects

In variant projects with branched documents, baseline behavior has additional considerations:
  • Overwriting upstream items in branched documents loses all links except the “is branched from” link
  • Polarion cache may need clearing after branching operations
  • Baselines should be identified by document ID/path rather than other identifiers for reliability
Cache clearing procedures after branching depend on your Polarion server configuration. Consult your Polarion administrator for the correct steps.

Verification

After resolving the issue:
  1. Navigate to Menu > Document > Show Baselines
  2. Select a baseline from the list
  3. Confirm the comparison view loads and shows change indicators for added, removed, and modified items
You should now see the baseline comparison view with color-coded highlights indicating changes between the current document state and the selected baseline. The comparingTo parameter appears in the browser URL, confirming comparison mode is active.

See Also

Support TicketsSource Code
  • RisksheetProjectProperties.java
  • NewBaselineCommand.ts
  • ComparisonManager.ts
  • RisksheetViewServlet.java
  • RiskItemsODataCollectionView.ts