This issue directly relates to JRA-24558, which has been marked fixed for JIRA 4.4.3.

After some testing with the new release, I found that filters and dashboards are still not recognized. Issues, however, have been fixed.

Reproduce

• Create a user with username "testuser"
• Login with username "testuser"
• Create a new issue filter and a new personal dashboard
• Inside the LDAP directory, create a username "TestUser"
• Move the LDAP directory to the top
• Going back to the dashboard as "TestUser" results in using the default system dashboard
• Going to 'Manage Filters' does not show the newly created filter.

I also created a new personal dashboard for "TestUser". In the database under the portalpage table, you can see that both "testuser" and "TestUser" is listed for their own personal dashboards.

In the previous report (JRA-24558), this was also mentioned:

This error happens because JIRA is using the column user_name in the table cwd_user for all operations. JIRA should have used the column lower_user_name. For example, the table jiraissue is showing "Administrator" in the column reporter for ticket B.

I did some SQL logging and found that JIRA still uses user_name for references.