Skip to main content

​
Why can’t I save changes to my risksheet?

Save failures typically occur due to Polarion permission restrictions, session timeouts, or conflicting concurrent edits by multiple users. Verify you have write permissions for the document and affected work items, check if your session expired (re-login may be required), and ensure another user hasn’t locked the document for editing. Network interruptions during save operations can also cause failures—check browser console for error messages. See Save Operation Failures for detailed diagnostic steps and Permission-Based Field Restrictions for permission troubleshooting.

​
The RISKSHEET menu disappeared after updating—how do I fix it?

Menu disappearance after updates is caused by multiple plugin versions accumulating in the Polarion Extensions directory. When copying a new RISKSHEET version over an existing installation instead of completely deleting the old folder first, plugin initialization fails due to conflicting files. To fix: stop Polarion, navigate to the Extensions directory, completely delete all RISKSHEET folders, extract the new version, verify only one RISKSHEET folder exists, then restart Polarion. See Menu Disappeared After Update for step-by-step recovery and Update RISKSHEET for proper update procedures.

​
Why are linked items not rendering correctly?

Link rendering issues occur when target work items are deleted, permission restrictions prevent access, or link role configurations are invalid. RISKSHEET cannot display links to work items you lack permission to read, and broken references to deleted items cause empty cells or error messages. Verify target items exist, check your Polarion permissions cover linked projects, and validate link role compliance using the nextedy.risksheet.checkLinkRoleCompliance configuration property. See Link Rendering Issues for diagnostic steps and Configure Cross-Project Linking for multi-project link configuration.

​
How do I fix “Access Denied” errors?

Access denied errors result from insufficient Polarion permissions for the document, work items, or project. RISKSHEET respects Polarion’s role-based access control—if you cannot edit work items in standard Polarion, you cannot edit them in RISKSHEET. Verify your Polarion role includes read/write permissions for the target document type and work item types, check project-level access restrictions, and ensure you’re not attempting to edit system fields restricted to administrators. See Access Denied Errors and User Roles and Permissions for permission architecture.

​
Why won’t my session stay active?

Session timeouts occur when Polarion’s configured session inactivity limit is reached, typically 30-60 minutes depending on server configuration. RISKSHEET inherits Polarion’s session management—inactive tabs or background windows don’t maintain session activity. To prevent timeouts during long editing sessions, periodically interact with the risksheet (scroll, edit cells) or increase Polarion’s session timeout in server configuration. Automatic save doesn’t prevent timeout. See Session Timeout Errors for timeout handling and recovery strategies.

​
What should I do when cells won’t let me edit values?

Cell editing restrictions occur due to field-level permissions, read-only configuration properties, or system field limitations. Polarion enforces field-level permissions separately from document permissions—you may have document write access but lack permission for specific custom fields. Check if the field is configured as read-only in the risksheet configuration, verify your Polarion role includes permission for that custom field, and confirm you’re not attempting to edit restricted system fields like Resolution. See Cell Editing Issues and Permission-Based Field Restrictions for field-level troubleshooting.

​
Why do exports omit calculated columns?

Calculated columns missing from exports indicate the export configuration doesn’t include server-rendered calculated columns, or the export format doesn’t support dynamic formulas. PDF and Excel exports require explicit configuration to include calculated columns—by default, only direct work item fields export. Enable calculated column export in configuration and verify formulas evaluate successfully before export. Client-side calculated columns may not export at all depending on export engine limitations. See Calculated Columns Missing in Exports and Export to Excel for export configuration.
Run through these checks for 80% of common issues:
SymptomFirst CheckSecond CheckThird Check
Can’t savePolarion permissionsSession timeoutConcurrent edit conflict
Menu missingMultiple plugin foldersIncomplete updatePolarion restart needed
Links brokenTarget item existsCross-project permissionsLink role compliance
Access deniedDocument permissionsWork item permissionsProject-level access
Session expiredInactivity timeoutNetwork interruptionPolarion server restart
Can’t edit cellField-level permissionsRead-only configurationSystem field restriction
Escalate to Nextedy support when:
  • Issue persists after following troubleshooting guides
  • Problem affects multiple users across different browsers
  • Polarion server logs show RISKSHEET-related errors
  • Recent update introduced new behavior
  • Configuration changes don’t resolve documented issues
Before contacting support, gather:
  • RISKSHEET version number
  • Polarion version and build
  • Browser and OS versions
  • Steps to reproduce the issue
  • Polarion server logs (if accessible)
  • Screenshots of error messages
Support TicketsSource Code
  • OpenHelpCommand.ts