Details

    • Sprint:
      CFAMX 2019R3 Sprint 2, CFAMX 2019R3 Sprint 3, CFAMX 2019R3 Sprint 4
    • SCRUM Team:
      Globogym Purple Cobras
    • SOW (Time Tracking) Project:
      44918
    • Work Type Classification:
      Sustaining

      Description

      As a Product Owner I want this feature to be tested from End To End so that I can sign off that it's been tested in the way in which it will be used in Production

      Use Case - Switch Off Suggested Ordering

      A user at a Suggested Ordering Store, is assigned permissions that allows them to access the Order Settings Page

      • Config > Show Suggested Details = True (Not required for this feature, but makes it a SO store)
      • Config > Display Order Settings Page = True
      • The two security settings should be independent of one another, but in reality, if a user has access to one, they will most likely have access to both
      • Security > Settings - Orders - Can Edit Build To = True
      • Security > Settings - Orders - Can Zero Suggested Quantity = True

      The user wants to Switch Off Suggested Ordering

      • To do this the user goes the to the Order Settings page and selects the "Set Suggested Quantity to Zero" setting
      • Now the user creates an order, for a vendor that normally has suggested items (For example: Maines/MBM/QCD/Food Authority)
      • When the order is created, the Quantity Ordered, is set to Zero
        • The only exception for this is for those items that have a Default Order Quantity Configured, that is greater than zero
        • Note: The default Order Quantity can be reduced due to an allocation
      • All details in the Suggested Details Panel should reflect what the Suggested Quantity would have been, if the user had allowed the Suggested Order algorithm to suggest the Quantity
      • When the order is placed, the SO Export is fired and there is a record in the resulting file that indicates that the Suggested Quantities were set to zero at the store level
      • Confirm that the data in the export is accurate and reflects the Suggested Details, even though the order was overridden to suggest zero
      • The order is later received
      • When the order is received, the SO Export is fired and there is a record in the resulting file that indicates that the Suggested Quantities were set to zero at the store level
      • Confirm that the data in the export is accurate and reflects the Suggested Details, even though the order was overridden to suggest zero

      Use Case - Maintain Build To

      A user at a Suggested Ordering Store, is assigned permissions that allows them to access the Order Settings Page

      • Config > Show Suggested Details = True (Not required for this feature, but makes it a SO store)
      • Config > Display Order Settings Page = True
      • Config > Display Build To Column on Item Maintenance and Ordering = Follow Store Specific Configuration
      • The two security settings should be independent of one another, but in reality, if a user has access to one, they will most likely have access to both
      • Security > Settings - Orders - Can Edit Build To = True
      • Security > Settings - Orders - Can Zero Suggested Quantity = True

      The user wants to enter Build To for Non Suggested Items Only

      • To do this the user goes the the Order Settings page and selects Display Build To Column = Non Suggested Items Only
      • Now the user navigates to Item Maintenance, and is able to record Build To values for those items that are not marked as
        • Note: Build To, in this instance (where Config > Display Build To Column on Item Maintenance and Ordering = Follow Store Specific Configuration), is displayed in the Right Hand panel
      • If the user changes from the Default View to the Inventory View the Build To is still displayed
      • If the user Downloads the CSV, the Build To is accurately reflected
      • For those items that are suggested, the Build To cannot be maintained, and is represented as a '-' in the CSV Export
      • User creates an order, and wants to see the Build To quantities
      • When a new order is created, the Build To column is available in Manage Columns, and can be moved from Item Details into the main grid, and back out again
      • The Build To Quantity accurately reflects the values recorded in Item Maintenance
      • If Display Build To Column = Non Suggested Items Only, the Build To for Suggested Items is represented as a dash
      • Other scenarios:
        • User sets Display Build To Column = No Items (Do not display)
          • When this is selected, the Build To column is:
            • Not displayed in Item Maintenance
            • Not Included in the CSV Download from Item Maintenance
            • Not displayed on the Order Page, under either Item Details or Manage Columns
        • User sets Display Build To Column = All Items
          • When this is selected, the Build To column is:
            • Displayed in Item Maintenance (Right hand panel) - For ALL items
            • Included in the CSV Download from Item Maintenance - For ALL items
            • Displayed on the Order Page, under either Item Details or Manage Columns, and includes a value for ALL items

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                will.englefield Will Englefield (Inactive)
                Reporter:
                will.englefield Will Englefield (Inactive)
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 5h 40m
                  5h 40m
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 5h Time Not Required
                  5h

                    PagerDuty

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