Dear Atlassian Team,
I have encountered this issue under "Instance Health" plugin. I have googled and everyone says this is a bug in the "Instance Health" plugin. I want to confirm whether it is a bug or I should fix this issue. Could you please help regarding this issue.
The supported collations for the different databases can be found in this Knowledge Base article. It also describes the impact of using unsupported collation. Using an unsupported collation may work fine, but there are no guarantees.
I think your google searches have failed you.
It's not a bug in the slightest, the health check is picking up an unsupported configuration that you're using. I suspect there's a possible bug in JIRA in that it doesn't stop an install or startup when using an unsupported collation, but it's not a bug in the healthcheck. It's working correctly.
Petar's link explains all the stuff you need to understand why it's reporting this issue to you.
In my experience, it's caused two problems for me. There are probably others.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
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