A minor schema change has been made to the Crucible SQL Schema in 2.8. If you need to rollback to an earlier version, you will need to restore from a backup to do so. Be sure to take a backup before you upgrade.
Please also be sure to read the End of Life Announcements for FishEye/Crucible 2.8 .
- Test your upgrades in your test environment before rolling into production.
- Back up your entire Crucible instance (see Backing up and restoring Crucible data), i.e.
- If you are backing up your Crucible instance via the Admin interface, tick all of the 'Include' checkboxes (e.g. plugins, templates, uploads, SQL database, etc).
- If you are backing up your Crucible instance using the command-line interface, do not use any exclusion options.
If you are already running a version of Crucible, please refer to the Crucible upgrade guide.
Checking for Known Issues and Troubleshooting the Crucible Upgrade
If something is not working correctly after you have completed the steps above to upgrade your Crucible installation, please check for known Crucible issues and try troubleshooting your upgrade as described below:
- Check for known issues. Sometimes Atlassian finds out about a problem with the latest version of Crucible after the software is released. In such cases we publish information about the known issues in the Crucible Knowledge Base. Please check there for known issues, and follow the instructions to apply any necessary patches if necessary.
- Did you encounter a problem during the Crucible upgrade? Please refer to the guide to troubleshooting upgrades in the Crucible Knowledge Base.
- If you encounter a problem during the upgrade and cannot solve it, please create a support ticket and one of our support engineers will help you.