← Back to team overview

dhis2-devs team mailing list archive

Re: Event Date in Tracker Capture

 

Thanx a lot Elmarie. I'll add my comments

On Tue, Feb 23, 2016 at 12:42 AM, Elmarie Claasen <elmarie@xxxxxxxx> wrote:

> Hi Pamod,
>
> This is a.known bug reported as
> https://bugs.launchpad.net/dhis2/+bug/1514693
>
> Apparently it is on the roadmap for 2.23. May help if you go into the bug
> and report that it affects you too.
>
> Elmarie
> On 22 Feb 2016 13:11, "Pamod Amarakoon" <pamodm@xxxxxxxxx> wrote:
>
>> Dear All,
>>
>> How's the event date that's displayed in tracker capture calculated. Is
>> it the time stamp of the particular event record in database or the
>> converted time to UTC?
>>
>> eg: When i created an event for Feb 22 00:00 it's saved in database as
>> Feb 22 00:00 (localtime). But output of tracker capture is 1 day less ( I
>> assume to convertion to UTC).
>>
>> Thank you
>>
>>
>> --
>> Regards,
>> Pamod Amarakoon
>>
>> Confidentiality Notice: the information contained in this email and any
>> attachments may be legally privileged and confidential. If you are not an
>> intended recipient, you are hereby notified that any dissemination,
>> distribution, or copying of this e-mail is strictly prohibited. If you have
>> received this e-mail in error, please notify the sender and permanently
>> delete the e-mail and any attachments immediately. You should not retain,
>> copy or use this e-mail or any attachments for any purpose, nor disclose
>> all or any part of the contents to any other person.
>>
>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
> *This message and any attachments are subject to a disclaimer published at
> http://www.hisp.org/policies.html#comms_disclaimer
> <http://www.hisp.org/policies.html#comms_disclaimer>.  Please read the
> disclaimer before opening any attachment or taking any other action in
> terms of this electronic transmission.  If you cannot access the
> disclaimer, kindly send an email to disclaimer@xxxxxxxx
> <disclaimer@xxxxxxxx> and a copy will be provided to you. By replying to
> this e-mail or opening any attachment you agree to be bound by the
> provisions of the disclaimer.*
>



-- 
Regards,
Pamod Amarakoon

Confidentiality Notice: the information contained in this email and any
attachments may be legally privileged and confidential. If you are not an
intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this e-mail is strictly prohibited. If you have
received this e-mail in error, please notify the sender and permanently
delete the e-mail and any attachments immediately. You should not retain,
copy or use this e-mail or any attachments for any purpose, nor disclose
all or any part of the contents to any other person.

References