How do I upgrade RISKSHEET to a newer version?
Upgrading Nextedy RISKSHEET involves replacing the extension files on your Polarion server and restarting the Polarion service. Download the new version from the Nextedy support portal, stop the Polarion server, replace the RISKSHEET extension JAR files in thepolarion/extensions directory, and restart Polarion. Always create a backup of your Polarion installation and existing configurations before upgrading. See Update RISKSHEET for detailed step-by-step instructions.
Do I need to update my configurations after upgrading?
Most RISKSHEET upgrades are backward-compatible and do not require configuration changes. However, major version upgrades (e.g., 23.x to 25.x) may introduce new configuration properties or deprecate old ones. After upgrading, check the Changelog for breaking changes and review your existing configurations against the Configuration Properties Index to take advantage of new features.Will my existing risksheet documents work after upgrading?
Yes, existing risksheet documents are fully compatible across RISKSHEET versions. The underlying data is stored as standard Polarion work items, so upgrades only affect the presentation and functionality layers. Your risk items, links, and custom fields remain unchanged. However, you should validate critical workflows and custom configurations in a test environment before upgrading production systems.Can I roll back to a previous version if something goes wrong?
Yes, you can roll back to a previous RISKSHEET version by restoring the original extension files and restarting Polarion. This is why creating a backup before upgrading is critical. Keep copies of both the extension JAR files and your configuration files (.polarion/risksheet/ directories) to ensure a clean rollback. Test the rollback procedure in a non-production environment first to verify compatibility.
Upgrade Planning and Testing
What should I check before upgrading in production?
Before upgrading RISKSHEET in production, test the new version in a staging or test environment that mirrors your production setup. Verify that all custom configurations work correctly, test critical workflows (risk creation, linking, exports), validate integration with LiveDoc documents, and confirm that user permissions function as expected. Create a comprehensive pre-upgrade checklist including backup verification, downtime window planning, and rollback procedures. See Troubleshoot Administration Issues for common upgrade issues.How do I migrate RISKSHEET to a new Polarion server?
Migrating RISKSHEET to a new Polarion server involves copying both the extension files and the configuration directories. Install RISKSHEET on the new server following the Installation guide, then copy the.polarion/risksheet/ configuration directories from your original server to the new one. Your risksheet data (work items) is migrated as part of the standard Polarion project migration process. Verify license activation on the new server through the Polarion administration interface.
Are there version-specific compatibility requirements?
Yes, each RISKSHEET version is compatible with specific Polarion versions. Always check the Polarion Version Compatibility matrix before upgrading to ensure your Polarion server version is supported. Upgrading RISKSHEET may require upgrading Polarion first, or vice versa. Plan coordinated upgrades for both products to maintain compatibility.Migration Best Practices
What data should I backup before upgrading?
Create backups of the following before any RISKSHEET upgrade:- Complete Polarion server backup (database and filesystem)
.polarion/risksheet/configuration directories for all projects- Custom Velocity templates in
.polarion/templates/ - Current RISKSHEET extension JAR files (for rollback)
- License key and activation information
- Custom column configurations and saved views
How long does a typical upgrade take?
RISKSHEET upgrades typically take 15-30 minutes including server restart time. The actual file replacement takes only a few minutes, but Polarion restart and initialization can require 10-20 minutes depending on your server size. Plan for a 1-hour maintenance window to allow time for testing and potential rollback if issues occur.Upgrade Process Overview
Version-Specific Considerations
| Upgrade Path | Key Considerations |
|---|---|
| 23.x → 24.x | Minor configuration updates, new formula functions available |
| 24.x → 25.x | Major release: review deprecated properties, test custom renderers |
| Any → Latest | Check Polarion version compatibility, validate license compatibility |
Related Topics
- Administration: Update RISKSHEET • Troubleshoot Administration Issues
- Compatibility: Polarion Version Compatibility • Changelog
- Configuration: Configuration Properties Index • Template Path Configuration
Sources
Sources
Support Tickets