Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-6556

Rice Dev: Principal ID search on Person lookup is case sensitive

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0-rc2, 2.0
    • Component/s: Unit Testing
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-6687Person lookup isn't case-insensitive in Rice 2.0
      KULRICE-4175Group Lookup - Group Name search is case sensitive
      KULRICE-7171Document type field on document search seems to be case sensitive in Rice 2.0
      KULRICE-7060KIM Person Maintenance screen allows a new user to be created with mixed-case or uppercase letters in Principal Name field
      KULRICE-7438Doc search: initiator is case sensitive
      KULRICE-13167Person lookups not ignoring case while doing wildcard searches
      KULRICE-14020Analysis: Wildcard fields are case sensitive for permissions
      KULRICE-4350Delegate Rule Lookup - Search by Person Reviewer not working correctly
      KULRICE-5521Rice Dev: Group Lookup bombs if Principal Name is added
      KULRICE-5523Rice Dev: Permission Lookup bombs if Principal Name is added
    • Rice Module:
      KNS, KRAD, KEW
    • Application Requirement:
      Rice
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      If you do a person search and put in a principal id of e*, for example it auto-capitalizes it and doesn't return any results. It's doing an exact case mach on the principal id so nothing gets returned. You can't force it to lower case either. Should be case insensitive.

        Issue Links

          Activity

          Hide
          Sona Sona (Inactive) added a comment -

          Do we want all our equals search to be case insensitive? Right now i have put a fix in for the wild card (LIKE query to be case insensitive, but that still leaves the question of what is expected when the end user types in the name without a *) should that be treated as case sensitive search?

          Show
          Sona Sona (Inactive) added a comment - Do we want all our equals search to be case insensitive? Right now i have put a fix in for the wild card (LIKE query to be case insensitive, but that still leaves the question of what is expected when the end user types in the name without a *) should that be treated as case sensitive search?
          Hide
          Sona Sona (Inactive) added a comment -

          Wildcard searches are now case-insensitive. Non-wildcard are still case sensitive.

          Show
          Sona Sona (Inactive) added a comment - Wildcard searches are now case-insensitive. Non-wildcard are still case sensitive.
          Hide
          Matt Sargent added a comment -

          Validated in Dev1 today and this works great now. Thanks!
          -Matt

          Show
          Matt Sargent added a comment - Validated in Dev1 today and this works great now. Thanks! -Matt
          Hide
          Jessica Coltrin (Inactive) added a comment -

          Closing since these items are now in the release notes.

          Show
          Jessica Coltrin (Inactive) added a comment - Closing since these items are now in the release notes.

            People

            • Assignee:
              Sona Sona (Inactive)
              Reporter:
              Matt Sargent
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel