Uploaded image for project: 'JOC - JS7 Operations Center'
  1. JOC - JS7 Operations Center
  2. JOC-2092

Daily Plan Projections - behavior for creating projections

    XMLWordPrintable

Details

    Description

      Current Situation

      • Web Service - generate Projections behavior
        • Two groups are generated:
          • Planned - marked in GUI in green (planned=true in JSON)
            • These entries correspond to DailyPlan entries that have already been planned/submitted.
            • The date range for these items consists of two ranges:
              • 2 months before generation date
                • used to display "old" entries e.g. for visual comparison with calculated projection items.
                • the 2-month value is hard-coded and not configurable.
              • Until last available planned date
            • Example:
              • Settings-dailyplan->projections_month_ahead=6
              • Generation date: 2025-08-21
              • Planned first day: 2025-06-21 (2 months ago)
              • Planned last day: 202x-xx-xx (last planned date)
            • Issue: Instead of a fixed Settings-dailyplan->projections_month_ahead months, the range ends at the last date already planned/submitted in the DailyPlan.
            • Issue: If a planned date contains no periods (e.g. all orders for this date were manually removed), the date is not marked as planned.
              • As a result, projections are incorrectly generated for this date.
          • Projections - marked in GUI in orange
            • Calculated projections based on schedules with the "Plan Order Automatically" definition.
            • Generates projections from a start point according to the Settings-dailyplan->projections_month_ahead for <n> months ahead (including the last day of the month).
            • Issue: Currently, the start date internally uses the last planned date.
              • If a DailyPlan is manually generated for 1 day a month in advance, the projection takes that day, creating a gap for the month.
              • If a DailyPlan is manually generated for 1 day a year in advance, the projection may not generate any entries if the Settings-dailyplan->projections_month_ahead setting is less than 1 year.
      • GUI
        • Calendar View
          • Issue: If a planned date contains no periods, the GUI shows an empty green field instead of displaying 0 as the number of periods.
        • Calendar View - Yearly
          • Issue: If "Inverted Projections" is checked, only the days of the month are displayed in the calendar, but not the number of inverted periods.
        • Export Function
          • Issue: if a planned date contains no periods, this date is missing in the export file.
        • Date View
          • Check Box: “Current Controller”
            • Checked
              • Planned and projection data (workflows, schedules, periods) are visible for the selected date - OK.
              • Issue: If "Inverted Projections" is checked, no data about workflows etc. is displayed.
            • Not checked
              • Planned
                • Issue: New column “Controller ID” is added but empty.
              • Projections
                • Issue: Data about workflows, schedules, and periods is completely missing.

      Desired Behaviour

      • Web Service - generate Projections behavior:
        • Planned
          • Instead of the hard-coded 2 months, a new setting is introduced: Settings-dailyplan->projections_month_before . Default=2.
          • Start date should be the first day of the month (not exactly <n> months before).
          • End date should extend <n> months after the generation date, according to the Settings-dailyplan->projections_month_ahead setting (including the last day of the month).
          • A date should still be marked as planned even if no periods exist (i.e., a DailyPlan entry without periods should not be treated as "not planned").
        • Projections
          • Should start calculation from the actual start date and generate projections for all dates in the range except the dates that are already planned.
          • End date should extend <n> months after the generation date, according to the Settings-dailyplan->projections_month_ahead setting (including the last day of the month).
      • GUI
        • The GUI should correctly display all planned and projection data without missing workflows, schedules, or periods.

      Test Instructions

      • Generate the DailyPlan for a new date (or use an existing one) and remove all orders.
        • Expected result: After projections are re-created, the date is marked as planned and the calendar view shows 0 periods.
      • Generate the DailyPlan for a new date 1 month in advance.
        • Expected result: After projections are re-created, no gap occurs.
      • See GUI-related issues
        • e.g. check all GUI filters and the Export function

      Attachments

        Activity

          People

            ZtRahul193 Rahul Patidar
            re Robert Ehrlich
            Aakash Rao Aakash Rao
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: