Tracker Event Date changes to previous day on refresh

[Ant Snyman]

I posted a complete description of the bug (with the subject "Issue with tracker - is it a feature or a bug?") on dhis2_devs with screen shots from Sierra Leone. I also demonstrated this to Ola and Markus while in Livingstone, Zambia and they confirmed that this is a bug (not just incorrect configuration).

In short: when creating an event, the initial event date is displayed correctly, but when refreshing the screen or going out of event capture and back in again the event date has changed to the previous event date minus 1 day.

[Markus Bekken (markus-bekken)]

It seems the bug is happening when the server is run on a machine that is not at UTC+0 time. Somehwere in the events API the date is translatedfrom UTC to local time, and then it is served to the client as UTC. This is not happening when retreiving single events, only when retreiving a list.

[Pamod Amarakoon (pamodm)]

Hi,

I also experienced the same on an instance running on a server UTC+05.30. I used web api to post events. The date appears correctly on a the database. But on display at tracker capture, it seems to display the date in UTC format disregarding the database date.

Hope this will be fixed soon.

Thanx

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.