Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-20598

Testing Clone 2022.R3 S3 - Suggested Count MxC Export - Date Picker Update

    Details

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

      Description

      Story

      As a user, I would like to only select 1 date to run the suggested count export.

      Single Date Picker Example - This date picker is in

      Displayed Date Example

      Story Goal

      The goal of this story is to fix the date range issue with Suggested Count Export data. We will require the user to select a single date. The export should then search all stores in the suggested count zone for a monthly count with an applied date within 30 days of the user selected date. This range should also include the user selected date in the search. If an applied date for a monthly count falls within this search criteria, the data from this or these monthly count(s) should populate the export. If there are no applied monthly counts for a store in the suggested count zone within the search dates, the items from the monthly count should populate along with the store info but the rest of the data should be blank.

      AC

      1. The Date Picker in the MxC suggested count export only allows the user to select one date instead of a date range.
        1. This is different that any other export in MxC. For the Suggested Count Export exclusively the text in the Date Range dropdown should change from "Today, Yesterday, Custom Range" to "Today, Yesterday, Custom Date"
        2. There should also be a Calendar Icon as we use this elsewhere in the site when selecting a single date.
        3. When the user selects "Custom Date" pop up a single calendar.
        4. Sundays and other closed days are not selectable in this calendar.
        5. The user selected date displays in the field. See example
      2. The user selected date serves as the end date of the search. The export returns data looking back 30 days from the user selected end date.
        1. If there is a monthly count with an applied date between the search dates, return all data requested by the export for that count.
        2. If there is no monthly count with an applied date between the search dates, return all the items from the monthly count as well as the corresponding store description info and leave the rest of the data fields blank.
      3. All stores in the suggested count zone populate the export in all monthly states:
        1. Applied count
        2. No Count
        3. Draft count
          1. With suggested count values applied
          2. Without suggested count values applied
      4. The export can and should return duplicate items for a store where there are more than one applied monthly count within the user selected date range.
        1. When there is more than one applied monthly count within the range, the count data returned for each item is in accurate.
      5. When the user chooses "Today", assuming "Today" is not a Sunday or an otherwise closed day, the export data is exactly the same when run from MxC or MMS.
        1. If we find problems related to this line of AC, please let me know so that we can address these issues

        Attachments

        1. CustomDate.png
          199 kB
          Jason Powell
        2. DatePicker.png
          104 kB
          Jason Powell
        3. SingleDateExample1.png
          91 kB
          Jason Powell

          Issue Links

          1.
          Create Test Scripts QA Task Done Unassigned

          0%

          Original Estimate - 0.5h
          Time Not Required
          2.
          Review Test Scripts QA Task Done Unassigned

          0%

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

          0%

          Original Estimate - 0.5h
          Time Not Required
          4.
          Execute Test Cases QA Task Done Unassigned

          0%

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

          0%

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

          0%

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

          0%

          Original Estimate - 0.5h
          Time Not Required
          8.
          Story Documentation Dev Task Done Unassigned

          0%

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

          100%

          Original Estimate - 8h
          Time Spent - 8h
          10.
          Testing in Staging QA Task Done Charles Wheeler

          100%

          Original Estimate - 8h
          Time Spent - 11m Time Not Required

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 20h
                  20h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 8h 11m Time Not Required
                  8h 11m

                    PagerDuty

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