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

M2 - Historical Dispatch Date column is not Localized

    Details

    • Type: Sprint Defect
    • Status: Done (View Workflow)
    • Priority: Major
    • Resolution: Completed
    • Affects Version/s: CFA 2023R4
    • Fix Version/s: CFA 2023R4
    • Component/s: Workflow
    • Labels:
      None

      Description

      Details
      M2 - Historical Dispatch Date column is not Localized

      Testing Environment Details
      Effected Server: All
      Build: Trunk - 23.07.232.5614
      Affected: M2
      iPad Version: 14.4.1
      Store(s): 01580 - Founders Parkway FSU
      Logged in User: pseudo_locale

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

      Steps to Reproduce:
      1. Login to MxNext as pseudo_locale
      2. Switch to store 01580 - Founders Parkway FSU
      3. Click Workflow icon
      4. Click Deposits (Despachar)
      5. Click Historial

      Expected Result
      Dispatch Date Column should be localized to the correct date/time format.

      Actual Result
      Dispatch Date column is not localized

        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 - 1h
                  1h
                  Remaining:
                  0h
                  Logged:
                  Time Not Required
                  Not Specified

                    PagerDuty

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