Hi, i have JIRA running MS SQL Server with collation 'SQL_Latin1_General_CP1_CI_AS' with versions 5.2.9, 6.1, 6.2, 6.3, 6.4 it worked fine
i just upgrade to 7.2.0 version and now i found the message:
the database collation 'SQL_Latin1_General_CP1_CI_AS' and table collation ''SQL_Latin1_General_CP1_CI_AS' are not supported by JIRA.
also, if i search documentation abount installation of JIRA with sqlserver2012 i found that the recomendation is CASE INSENSITIVE
so what do i have to do in this case?
Change your database collation to Latin1_General_CI_AI and the health check will no longer show error.
(Always make changes on test database in a test jira environment before doing in prod)
i changed the collation, and i receive the error
"Argument data type ntext is invalid for argument 1 of lower function". in log file, with table: "AO_54307E_VIEWPORTFORM"
when i try add sla based of requesttype specifycally in JQL filter
what should i have to do?
Did anyone ever receive a resolution to this issue? We are encountering the same issue. I've created a fresh database, set the collation accordingly, imported all the data from the prior database into the new database with the correct collation, and now jira wants an installation key. After providing the key, the installed version thinks there is no data. Is there a suggestion for resolving this issue?
Hi Atlassian community, My name is Max and I work on the product integration team at Atlassian. I am pleased to announce the early access program for the Jira Cloud add-in for Outlook. This add-in...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events