openerp-india team mailing list archive
-
openerp-india team
-
Mailing list archive
-
Message #14485
[Bug 1037466] [NEW] Time Problem in Leads History (6.1)
Public bug reported:
There is a problem with the time in leads history. When you change the
state of a lead or if you send an email or add an internal note, a line
is added in the 'Communication & History' tab. But, there is a problem
with the date, it ignores the timezone. The time which is indicated in
the history is the GMT time (server time).
So, for now, for example in Belgium, there is a two hour gap between the
time indicated in the history and the real time of the event (change
state, email received or sent, ...).
This bug happens on version 6.1 (not tested on other versions)
I think, writing the time in the message of the history is not a good
idea. It should be better to have two columns in the history: date and
message.
Thanks.
** Affects: openobject-addons
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/1037466
Title:
Time Problem in Leads History (6.1)
Status in OpenERP Addons (modules):
New
Bug description:
There is a problem with the time in leads history. When you change
the state of a lead or if you send an email or add an internal note, a
line is added in the 'Communication & History' tab. But, there is a
problem with the date, it ignores the timezone. The time which is
indicated in the history is the GMT time (server time).
So, for now, for example in Belgium, there is a two hour gap between
the time indicated in the history and the real time of the event
(change state, email received or sent, ...).
This bug happens on version 6.1 (not tested on other versions)
I think, writing the time in the message of the history is not a good
idea. It should be better to have two columns in the history: date
and message.
Thanks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/1037466/+subscriptions
Follow ups
References