-
Bug
-
Resolution: Won't Fix
-
Medium
-
None
-
4.1.1
-
4.01
-
Steps to reproduce:
- Create JIRA db with case insensitive collation
CREATE DATABASE jiradb CHARACTER SET utf8 COLLATE utf8_general_ci;
- Add two workflows, one called 'ABC' and the second one 'abc'.
- Create new workflow scheme e.g 'myscheme' and assign the 'ABC' workflow to it.
- If you navigate to the Workflows page, you notice that both workfows have been associated with the scheme.
JIRA generates the association between the workflows and the scheme with help of following SQL queries:
"SELECT ID, SCHEME, WORKFLOW, issuetype FROM workflowschemeentity WHERE WORKFLOW='ABC'" "SELECT NAME, DESCRIPTION FROM workflowscheme WHERE ID='10020'" "SELECT ID, SCHEME, WORKFLOW, issuetype FROM workflowschemeentity WHERE WORKFLOW='abc'" "SELECT NAME, DESCRIPTION FROM workflowscheme WHERE ID='10020'"
- is related to
-
JRASERVER-21442 Incorrect character comparison between different collation for MySQL
- Closed
-
JRASERVER-42503 Recommended Collation for SQL Server Database
- Closed
- relates to
-
JRASERVER-21506 JIRA upgrade process is not fully compatible with case sensitive collation
- Closed