Best practices for Crucible configuration
1. Set up a separate FISHEYE_INST folder location on the same system for Crucible's data.
This will allow for easy upgrades of the core program and neatly separated data backup.
2. Run Crucible on a dedicated machine, accessing its data on the local file system.
This is the best environment for swift Crucible performance. Avoid running Crucible in a virtual environment.
3. Do not give Crucible projects the same key as your JIRA projects.
When naming projects, take care to ensure that the key you assign to them is not the same as any of your JIRA projects. The reason for this is, if one of your Crucible projects has the same key as one of your projects in JIRA, then all links with that key will lead back to Crucible, rather than leading to JIRA, removing the ability to navigate between the two applications.
To avoid this, name your Crucible project keys differently. For example, you could place the following text at the beginning of each project key:
CR- to distinguish it. So, for this case, if you have an existing JIRA key of '
RHUBARB', you would create a Crucible key called '
CR-RHUBARB' so that they do not conflict.
4. Do not use the built-in HSQLDB database for production use.
The Crucible built-in database, running HSQLDB is somewhat susceptible to data loss during system crashes. We recommend that you do not use HSQLDB for production systems. External databases are generally more resistant to data loss during a system crash and are more suited for production use.