I just updated to JIRA 6.15, HUGE MISTAKE once again jumping on Atlassian upgrades as they are POORLY TESTED and Q/A is a total failure! Beyond that, the error in my log file is:
2016-04-21 19:42:23,320 JiraTaskExectionThread-2 WARN neal007 1181x651x1 1m5o77x 184.108.40.206 /secure/admin/IndexReIndex.jspa [c.a.jira.index.AccumulatingResultBuilder] com.atlassian.cache.CacheException: com.atlassian.cache.CacheException: com.atlassian.cache.CacheException: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT KEY, CUSTOMFIELDTYPEKEY, CUSTOMFIELDSEARCHERKEY, cfname, DESCRIPTION, defaultvalue, FIELDTYPE, PROJECT, ISSUETYPE FROM dbo.customfield WHERE ID=? (Incorrect syntax near the keyword 'KEY'.)
I looked in the SQL Database schema for the table "customfield" and there is no column "KEY" defined. Was one supposed to be added or is this a bad SQL statement in JIRA 6.1.5 that kills it???
I'm dead in the water, again!
This is a perfect example of Atlassian's lack of Q/A in testing new releases. Had anyone actually run an upgrade from 6.1.4 to 6.1.5 using MS-SQL or MySQL it would have failed. They rely too much on automated testing and distribution which is why I personally, as a software developer and software company owner despise when people rely solely on automated Q/A. This is the second time in recent past they have broken an upgrade against MS-SQL at least.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot