A day is a day, no matter if you are at Paris, New York or Tokyo, 2025-09-16 should be the same day for everyone. Currently in Tuleap we handle date and datetime the same way: they are a point in time and we display it with the current user timezone. As 2025-09-16 is stored as 2025-09-16 00:00 in database, from another timezone it can be displayed as 2025-09-15 leading to confusion in teams.

But semantically date and datetime are not the same thing, the first one should represent a day when the second one represent a point in time.

The fact is that in some places in Tuleap, date are already handled as day: backlog releases list, burnup and burndown graphs. But not everywhere.

Proposed solution

To fix that, we'll now store date values with the timezone of the changeset submitter. This way, when the date is displayed, we display it with the submitter timezone and not the viewing user timezone, everyone will see the same date.

This does not apply to datetime fields, they remain as they are currently.