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

R2 Patchback CLONE - Sales Exclusions - Not Showing Up When Created

    Details

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

      Description

      Details

      Some newly created Sales Exclusions are not displaying in stores that they are assigned to.

      Steps to Reproduce

      1. Create a new sales exclusion. Example:
        1. 9888 New Store 2
        2. Assigned to Store: 000442'

      Expected Functionality

      The sales exclusion displays in store 00442

      Actual Functionality

      The sales exclusion does not display in store 00442

        Attachments

        1. Display.png
          Display.png
          244 kB
        2. Create.png
          Create.png
          182 kB

          Issue Links

          Clones

          Testing Defect - CFAMX-24659 Sales Exclusions - Not Showing Up When Created (R2 Patchback Clone Linked)

          • Major - Major loss of function.
          • Done

            Activity

              People

              • Assignee:
                Sharon.Madihlaba Sharon Madihlaba
                Reporter:
                jason.powell Jason Powell
              • Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

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

                    PagerDuty

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