Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • SCRUM Team:
      Great White
    • Story Points:
      1
    • Work Type Classification:
      Sustaining

      Description

      As a user, I would like the "Select a Store" modal search to show me fresh results when initiate a new search.

      Details

      Data Export Store Search Workflow to optimize:

      • Search for and select several stores in the Select A Store modal
      • From the table in the data export page, deselect at least one of your selected stores
      • Open the Select a Store modal again. You should see your list of selected and deselected stores.
      • Enter new search criteria that is distinct from the selected and deselected stores in the modal and initiate a new search.

      What we currently see when we perform this action is the list of results is blended with results from the previous search. New search hits and deselected stores are at the top of the list and
      selected stores are at the bottom.

      What we would like to see happen is that when a new search string is entered, we get a fresh set to search results meaning we keep the selected stores at the bottom of the results list but
      we return a new set of results in the top of the list. We should not keep the previous, deselected, stores in the list unless they match the new search string. Fresh search = fresh results.

      AC

      1. Each time the user enters a new search in the Select a Store modal, the search hits are fresh and specific to the most recently entered search string.
      2. If there are selected stores in the modal from a previous search, those stores should persist at the bottom of the hits list and continue to be selected.

        Attachments

        1. screenshot-1.png
          22 kB
          Jason Powell
        2. screenshot-2.png
          39 kB
          Jason Powell
        3. screenshot-3.png
          34 kB
          Jason Powell
        4. screenshot-4.png
          18 kB
          Jason Powell

          Issue Links

          1.
          Review Test Scripts QA Task Done Unassigned

          0%

          Original Estimate - 0.5h
          Time Not Required
          2.
          Deploy QA Task Done Unassigned

          0%

          Original Estimate - 0.5h
          Time Not Required
          3.
          Functional Review with QA Dev Task Done Unassigned

          0%

          Original Estimate - 0.5h
          Time Not Required
          4.
          DIT Dev Task Done Unassigned

          0%

          Original Estimate - 0.5h
          Time Not Required
          5.
          Design Review Dev Task Done Unassigned

          0%

          Original Estimate - 0.5h
          Time Not Required
          6.
          Testing in testing QA Task Done Charles Wheeler

          100%

          Original Estimate - 1h
          Time Spent - 1h
          7.
          Testing in staging QA Task Done Charles Wheeler

          100%

          Original Estimate - 1h
          Time Spent - 1h

            Activity

              People

              • Assignee:
                charles.wheeler Charles Wheeler
                Reporter:
                jason.powell Jason Powell
              • Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 4.5h
                  4.5h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 2h Time Not Required
                  2h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.