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

Inventory Adjustment History Not Displaying Grid Correctly on iPad Version: 14.4.1

    Details

    • Type: Sprint Defect
    • Status: Done (View Workflow)
    • Priority: Major
    • Resolution: Completed
    • Affects Version/s: CFA 2022R2
    • Fix Version/s: None
    • Component/s: Inventory
    • Labels:
      None
    • SCRUM Team:
      Brotherhood of Mutants
    • Sprint:
      2022.R2 New Features Sprint 4, 2022.R2 New Features Sprint 5

      Description

      Details
      Inventory Adjustment History Not Displaying Grid Correctly on iPad

      Testing Environment Details
      Effected Server: M2
      Build: CFA - 22.2.0.4841
      Affected: iPad
      iPad Version: 14.4.1
      Store(s): Any
      Logged in User: sysadmin

      Feature: N/A
      Related Tickets (Stories or Features): CFAMX-19243
      Other Related Links (Confluence, BRDs, Etc...): N/A
      Feature Configurations: N/A

      Steps to Reproduce:
      1. Login to M2
      2. Change Store to 00440 - Colony Square
      2. Navigate to Inventory Adjustments > History

      Expected Result
      All Data should be Displayed

      Actual Result
      Data Doesn't Appear to be displaying Correctly

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Tristan.Strong Tristan Strong
                Reporter:
                Tristan.Strong Tristan Strong
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 3h
                  3h
                  Remaining:
                  0h
                  Logged:
                  Time Not Required
                  Not Specified

                    PagerDuty

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