openerp-india team mailing list archive

["Olivier Dony \(OpenERP\)" <982881@xxxxxxxxxxxxxxxxxx>]

Indeed, the notification should be rendered with proper consideration to
the user's timezone (it will be stored in normal text that is not
converted upon display, as opposed to normal datetime fields that are
dynamically converted)

Development notes: for converting the timestamp according to the user's timezone there is a standard method in trunk: fields.datetime.context_timestamp() which will return a proper datetime object.
In this particular case we should be careful to print the timezone along with the timestamp in the message (when we call strftime() with the converted timestamp), because it may be seen by a lot of users in different timezones.

We could also imagine embedding widgets for rendering dynamic timestamps
inside a notification message (with values that are possibly different
from the message posting time), but that may be overkill for the few
cases where the notification text contains timestamps.

Thanks for reporting!

** Changed in: openobject-addons
   Importance: Undecided => Low

** Changed in: openobject-addons
       Status: New => Confirmed

** Changed in: openobject-addons
     Assignee: (unassigned) => OpenERP R&D Addons Team 1 (openerp-dev-addons1)

-- 
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/982881

Title:
  Feed notification time of meeting is different from actual meeting

Status in OpenERP Addons (modules):
  Confirmed

Bug description:
  Entering a meeting causes a notification  on the timeline with a wrong
  timestamp (See attached screenshot)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/982881/+subscriptions