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

CLONE - 2022R4 Patchback- M2 - Inventory Count - load page when clicking count option from menu after a Save, Apply or Delete

    Details

    • Type: Testing Defect
    • Status: Done (View Workflow)
    • Priority: Major
    • Resolution: Completed
    • Affects Version/s: CFA 2022R4
    • Fix Version/s: CFA 2022R4
    • Component/s: Counting
    • Labels:
    • SCRUM Team:
      Brotherhood of Mutants
    • Sprint:
      2022.R5 New Features Sprint 1

      Description

      Scenario : when a count (spot, weekly, monthly, or ANY count configured) is Saved or Applied or Deleted  AND the user receives the 'Inventory count successfully .....' toast. IF the user clicks the hamburger to display the menu options again, then clicks Input Inv. Counts AND then clicks the same count type that was just Saved, Applied or Deleted, the Inv. Count Item Detail page is not being loaded.

      Steps:

      1. Login to M2 Mobile
      2. Click Input Inv. Counts
      3. Click any count ( Spot, Weekly, Daily, Monthly,etc)
      4. Click some count values for 1 or more items
      5. Save or Apply or Delete the count and follow through to success message
      6. Click the hamburger 
      7. Click Input Inv. Counts
      8. Click the same count that was previously selected in step 3

      Defect:

      The count detail page is not loaded. The page remains blank. It should take me to the edit page of each of the counts.

       

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                charles.wheeler Charles Wheeler
                Reporter:
                Marwa.Abdelwahed Marwa Abdelwahed
              • Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

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