-
Suggestion
-
Resolution: Low Engagement
-
None
-
6
-
1
-
Issue Summary
Customer reports that when searching for users in Audit Log, the query is case sensitive. So, varying cases in usernames, displays name and e-mails may cause them not to be found. The same applies for groups.
Environment
Reproduced on
- Crowd 3.6 and 3.7
- Postgres
Steps to Reproduce
- Sample user name: Guest
- Access Crowd, got to Audit Logs
- In User filter, type 'guest'
- Delete the field content and type 'Guest'
- Delete the field content and type 'GUEST'
Expected Results
Find the user typed in either lower, upper or mixed cases
Actual Results
User can only be found if the username it is typed exactly as stored.
The query it performs in Postgres use comparison operation LIKE instead of ILIKE.
Excerpt from Postgres log:
[64807]: [565-1] user=postgres,db=crowd_360,app=PostgreSQL JDBC Driver,client=127.0.0.1 LOG: execute <unnamed>: select distinct entities1_.entity_name as col_0_0_, entities1_.entity_id as col_1_0_, entities1_.entity_type as col_2_0_ from cwd_audit_log_changeset auditlogch0_ inner join cwd_audit_log_entity entities1_ on auditlogch0_.id=entities1_.changeset_id where entities1_.entity_type=$1 and (entities1_.entity_name like $2) order by col_0_0_ ASC limit $3 [64807]: [566-1] user=postgres,db=crowd_360,app=PostgreSQL JDBC Driver,client=127.0.0.1 DETAIL: parameters: $1 = 'USER', $2 = 'Test%', $3 = '11'
Workaround
None at the moment. User name has to be typed in exact casing as it is stored.
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Crowd Data Center, please check our public roadmap.
Kind regards,
Crowd Data Center