In my environment I have JIRA 6.0.1 and Cruicible/Fishey 3.0.0 using the same database to store their data.
If I plan to upgrade JIRA from 6.0.1 and 6.1.9, should I worry about Cruicible/Fisheye db tables ?
Shall I stop Cruicible/Fisheye before migration ?
Thank you for help,
Are you actually using the same database (and not the same database server)? If indeed on the same database JIRA would complain about tables not belonging to the server on every restart, i know this because i once hosted an extra table in the JIRA database. This table was never really wiped, but JIRA might lock the database while doing it's upgrade, so it makes a lot of sense to shut down Crucible/Fisheye in that case. It would also make a lot of sense to create a separate database for the applications, in the same sense your movies, music and pictures are not in one single folder on your computer. At some point JIRA and Fisheye might not even accept that same database configurations as these projects can drift in different directions, and having it setup like this will cause you hell. Lucky for you most crucible tables are prefixed with cru_ (except for plugins which are prefixed A0 on both JIRA and Crucible).
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs