Planned dates of EAP Iterations not matching the synched Agile 2.0 sprint dates for few users

[Syed Azam]

In Enterprise Agile planning , the dates fields are glide_date fields, while in Agile 2.0 sprints, the dates are glide_date_time fields, So, when synching the EAP Iterations with sprint in Agile 2.0, the Agile 2.0 sprints are set by concatenating 00:00:00 to the date value.

For example: 

If EAP iteration has start date and end date as 10/10/2025 and 23/10/2025, In Database, the values of Agile 2.0 sprints are saved as 10/10/2025 00:00:00 and 23/10/2025 00:00:00

So, based on the timezone of the logged in user, these values can visually be different when comparing EAP dates with Agile 2.0 sprint dates.

So, from the above example: It is quite possible that a user from PST timezone will see the display value of Agile 2.0 sprints as 09/10/2025 HH:MM:SS and 22/10/2025 HH:MM:SS

Thus, these normalized values when converted from date to date time values can show different values for different users, while they are normalized to UTC value.