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

Investigate a method to trickle the Forecast Import

    Details

    • Sprint:
      CFAMX 2019R2 Sprint 5
    • SCRUM Team:
      Brotherhood of Mutants
    • SOW (Time Tracking) Project:
      44918
    • Work Type Classification:
      Sustaining

      Description

      In an effort to best support the roll out of 2,000+ stores for the forecast import, we need to continue to review options that will allow us to proceed in support of CFA.

      One thing that we have discussed is throttling/trickling the forecast over an extended period, rather than trying to import everything within a two hour window.

      • This is an option that CFA are open to us doing
        We should plan to support importing 2,000 full files and 2,000 summary files in a 10 hour period.
      • Start at 02:00 and end by noon

      Review the current process and look at options to process fewer forecasts at once while still achieving the goal of importing all available data in a 10 hour window, without spiking system resources.

      Acceptance Criteria

      1. Developer will write a testable story - CFAMX-2933

        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 - 13h 40m
                  13h 40m
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 10h Time Not Required
                  10h

                    PagerDuty

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