Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-15149

Don’t expose raw elasticsearch functionality by default

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 3.10.0
    • Fix Version/s: None
    • Component/s: Search
    • Labels:

      Description

      Searching is a confusing experience in NXRM3. People don’t realize they’re entering an elasticsearch string, so they don’t get the results they expect (e.g. dashes and forward slashes aren’t interpreted literally).

      Exposing raw elasticsearch functionality is probably the wrong approach anyway. It’s powerful and flexible, but does far more than most people need. Let’s introduce a translation layer that maps to the way people expect to use search (Shade Solon [X] can help us better understand user expectations).

      Acceptance criteria:

      • Treat search strings as partial matches in all fields (e.g. my.search.string is equivalent to *my.search.string*)
      • Allow people to do an exact match by surrounding their query in quotes (e.g. "my.search.string")
      • Work with Shade Solon [X] to figure out if there are any other expressions we need to support
      • Feature flag if there is worry of work crossing releases

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              dsauble Daniel Sauble
              Last Updated By:
              Joe Tom
              Team:
              Nexus - UX
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title