We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low (View bug fix roadmap)
    • None
    • None
    • None
    • None

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      According https://confluence.atlassian.com/adminjiraserver071/connecting-jira-applications-to-sql-server-2012-802592195.html JIRA 7 supports the following collations with SQL Server 2012:

      Collation type must be case-insensitive. We support 'SQL_Latin1_General_CP437_CI_AI' and 'Latin1_General_CI_AI' as case-insensitive, accent-insensitive, and language neutral collation types. If your SQL Server installation's collation type settings have not been changed from their defaults, check the collation type settings.

      The JIRA Instance Health says: Result OK
      with Message: The database collation 'Latin1_General_CI_AI' and table collation 'Latin1_General_CI_AI' are supported by JIRA.

      But in the atlassian-jira.log the following WARN message is logged:

      2016-03-24 10:45:50,754 JIRA-Bootstrap WARN [c.a.j.appconsistency.db.CollationCheck]

      ****************************************************************************************************
      You are using an unsupported mssql collation: Latin1_General_CI_AI. This may cause some functionality to not work.
      Please use SQL_Latin1_General_CI_AI or SQL_Latin1_General_CP437_CI_AI as the collation instead.
      ****************************************************************************************************

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • Icon: Bug Bug
              • Resolution: Duplicate
              • Icon: Low Low
              • None
              • None
              • None
              • None

                NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

                According https://confluence.atlassian.com/adminjiraserver071/connecting-jira-applications-to-sql-server-2012-802592195.html JIRA 7 supports the following collations with SQL Server 2012:

                Collation type must be case-insensitive. We support 'SQL_Latin1_General_CP437_CI_AI' and 'Latin1_General_CI_AI' as case-insensitive, accent-insensitive, and language neutral collation types. If your SQL Server installation's collation type settings have not been changed from their defaults, check the collation type settings.

                The JIRA Instance Health says: Result OK
                with Message: The database collation 'Latin1_General_CI_AI' and table collation 'Latin1_General_CI_AI' are supported by JIRA.

                But in the atlassian-jira.log the following WARN message is logged:

                2016-03-24 10:45:50,754 JIRA-Bootstrap WARN [c.a.j.appconsistency.db.CollationCheck]

                ****************************************************************************************************
                You are using an unsupported mssql collation: Latin1_General_CI_AI. This may cause some functionality to not work.
                Please use SQL_Latin1_General_CI_AI or SQL_Latin1_General_CP437_CI_AI as the collation instead.
                ****************************************************************************************************

                        Unassigned Unassigned
                        a3bcd8c82edf Michel Clément
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        1 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            a3bcd8c82edf Michel Clément
                            Affected customers:
                            0 This affects my team
                            Watchers:
                            1 Start watching this issue

                              Created:
                              Updated:
                              Resolved: