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

Forecast Usage - Forecast Range is not subtracting Sundays/Closed Days

    Details

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

      Description

      When viewing the Forecast Range, in the Forecasted Usage popover, Sundays are not being subtracted.

      • A quick test of this, and I noticed that if the range spans Sunday (order Friday Cover Until Monday), Sunday is subtracted.
      • If however, the Cover Until date falls on the closed date (Sunday), then the Forecast Range is incorrect, Sunday is not subtracted

      From Testing

      Reproduction Steps

      • Create Order
      • Select 6/27 for DD
      • Select 6/30 for CUD
      • Confirm
      • search for Chicken, Filets
      • Click on Chicken Filets
      • View Suggested Details panel
      • Click the i Icon for Forecast Usage

      Expected Results

      • Forecast Range = 2.11 Days

      Actual Results

      • Forecast Range = 3.11 Days

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

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

                    PagerDuty

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