Issue Summary

The customer noticed different work item totals between the Program Feature Backlog and the 4th chart on the Process Step Cycle Time (PSCT). (or named Porcess Flow Cycle Time (PFCT) report)
Our development engineer has deconstructed the stored procedure involved in rendering the fourth chart into logical subqueries. These were then run against the align support instance for data analysis. Our preliminary findings suggest that the issue might be centered around the handling of time zones within the stored procedure logic.

This is reproducible on Data Center: (yes)

Steps to Reproduce

1. Step 1. We move the one work item from Ready to start (total number changed from 2 to 1) to working (total number changed from 8 to 9)
   Time: AEST Time: 8:45AM Wednesday, March, 20, 2024 / UTC Time: 9:45 p.m. Tuesday, March 19, 2024
   

   To Do	Ready to start	Waiting to Start	Working
   5	1	1	9

   

   To Do	Ready to start	Waiting to Start	Working
   5	3	1	7

2. Step 2. Checked the report on 20/Mar/24 11:16 AM AEST, No change has been made on both Date and number of states.
   

   To Do	Ready to start	Waiting to Start	Working
   5	3	1	7

3. Step 3. Comparing the reports that ran on 20/Mar/24 11am AEST and 20/Mar/24 3pm AEST, the value has been changed.
   

   To Do	Ready to start	Waiting to Start	Working
   5	2	1	8

Expected Results

The same results are shown on the backlog and Process Flow Cycle Time (PFCT) report

Actual Results

It takes longer to update on Process Flow Cycle Time report because of how handling of time zones within the stored procedure logic.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available