Uploaded image for project: 'Confluence Server'
  1. Confluence Server
  2. CONFSERVER-19731

Group Search wildcarding inconsistent with User Search and with Append Wildcards option

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Low
    • Resolution: Won't Fix
    • Affects Version/s: 3.2.1
    • Fix Version/s: None
    • Component/s: None
    • Environment:

      Standalone on Unix.
      JDK 1.5.0_12

    • Internal Complexity:
      2
    • Internal Value:
      5

      Description

      In Confluence 3.2.1, it appears that the User Search function now optionally adds wildcarding BEFORE as well as after the specified search parameter. This occurs when the new Confluence Admin option "Append wildcards to user and group searches" is set to Yes. The User Search dialog works this way whether doing admistrative Manage Users or editing page restrictions. Yes is the default after upgrade.

      For large LDAP systems this can cause unexpected searious delays. We're were seeing 3-minute response times with the 3.2.1 system and didn't understand the cause without Atlassian support involvement.

      Request 1) Atlassian should document this functionality change for 3.2.1 upgrades for Administrators, perhaps. Did I miss it in the documentation?

      The prior implementation gave the user feedback by adding the wildcards to the specified parameter, so that the user can see the exact wildcarding implemented.

      Request 2) Restore the feedback functionality.

      The group search function, visible via the page restrictions edit dialog, apparently doesn't add a wildcard to the front of the specified parameter, even if the "Append wildcards to user and group searches" is set to Yes. Obviously the functionality and the option descriptor are inconsistent.

      Request 3) Make the option accurately reflect the functionality. Preferably, I guess someone may want to have the Group Search function changed rather than the option descriptor.

      Request 4) Bring back the old functinality. Add a new choice for the Back Only option.

      Wildcarding = No
      Wildcarding = Front and Back
      Wildcarding = BACK ONLY LIKE CONFLUENCE USED TO DO IT

      How hard would it have been to do that, and make the system backwards compatible?

      Request 5) Think about implementing future changes allowing backwards compatibility

      Thanks!

        Attachments

          Activity

            People

            • Assignee:
              shaffenden Steve Haffenden (Inactive)
              Reporter:
              joelthomson Joel Thomson
              Participants:
              Last Touched By:
              Katherine Yabut
            • Votes:
              2 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Last commented:
                4 years, 27 weeks ago