-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
5.1.1, 5.2.11, 6.2-OD-7, 6.2.1, 6.4-OD-14, 7.1.2, 7.9.1
-
5.01
-
16
-
Severity 3 - Minor
-
1
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Steps to Reproduce:
- Create a number of Groups with mixed cases
- Preview the People/Roles section of any project administration
- Attempt to add a group to any Project Role by typing into the Group's field
- The behaviour of the Group browser field can be quite erratic as shown in the attached screenshots. Basically the field will sometimes behave as case-insensitive.
Screenshot:
- case-insensitive behaviour after entering 1 character
- case sensitive behaviour after entering 2 characters
Notes
It is good to note that while it is not possible to create a group like 'Jira-users' (it will not be created due to this bug), it can still be created via import. When both 'Jira-users' and 'jira-users' exist on the instance, attempts to remove 'Jira-users' will instead remove 'jira-users'.
- duplicates
-
JRASERVER-13798 Remove case sensitivity from Group Names when searching
- Closed
- is a regression of
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-
[JRASERVER-33850] Groups Browser on Project Roles Search is Case-sensitive
How can such an important UX bug be unaddressed for 4 YEARS? This inconsistent behaviour is VERY confusing, and leads to unnecessary support calls.
Having to explain this to users without sounding completely mental is always a challenge. Please put this on your backlog!
Cameron Martin
added a comment - This really should be fixed. It must be utterly trivial to fix, but really confuses people, entrenches admin reliance and annoys the hell out of me. 
Cameron Martin
added a comment - This really should be fixed. It must be utterly trivial to fix, but really confuses people, entrenches admin reliance and annoys the hell out of me. This issue is in the list for the 2014 Grad crew.
If you have any questions about implementation then please chat to mlassau.
I'm disappointed this is still an issue after the UI refresh on the roles page a few versions ago. I'm tired of telling users why search doesn't work as they expect it to.