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

Search fields can be wiped out when changing from custom/non-custom

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: 3.0.0-m5
    • Fix Version/s: None
    • Component/s: Search, UI
    • Labels:
      None
    • Environment:
      Chrome MacOSX

      Description

      I just noticed that going from custom search (like maven) to search deletes anything entered in the keyword field.
      The inverse of this (going from search to custom search) keeps the keyword defined.
      Filing for eval, though I suspect a bug since inconsistant.

      Did not check older NX3 or NX2 at this time. Debug was off.

      Steps to repro:

      • Load search (was logged in as admin)
      • Enter a keyword (w/ results make it easier to see)
      • Change to a custom search. Note how the keyword field is added and content maintained.
      • Return to (base) search. BUG: Keyword field now says "Any".

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            jtom Joe Tom
            Last Updated By:
            Peter Lynch
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Date of First Response:

                tigCommentSecurity.panel-title