Resolution: Won't Fix
6.3, 6.3.15, 7.0.10
Severity 2 - Major
Atlassian Update – 31-10-2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, has a viable workarounds, so it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Won't Fix . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster
Error when attempting to upgrade JIRA
The following appears in JIRA's logs:
Upgrade tasks that update sequences do not correctly apply schema name to table when the schema is named "jira". This has recently been triggered by an upgrade task in JIRA 6.3, however it's possible it could affect any future upgrade tasks which contain an update to a sequence.
- Install a version of JIRA earlier than JIRA 6.3 on MS SQL Server, making sure that the schema JIRA is installed in is called "jira", and the default schema of the user JIRA connects to MS SQL Server is something other than "jira", for example "dbo" (which is the default). JIRA actually encounters problems if the default schema is not set to "dbo".
- Make sure it's all working fine
- Upgrade to 6.3 or above
- Watch the atlassian-jira.log file for the error above
One of the following works around the issue:
- Change schema name to something other than "jira". Update the dbconfig.xml file according to the changes.
- Stop JIRA
- Change the default schema of the database user JIRA is using to be "jira"
- Start JIRA
- Allow the uprade task to complete - some things in JIRA will be broken such as the streams plugin
- Stop JIRA
- Remove the directories <jira-home>/plugins/bundled-plugins and <jira-home>/plugins/.osgi-plugins
- Change the default schema back to "dbo"
- Start JIRA
- JIRA should be working again
This issue appears to be related to JRA-25270