Comment 3 for bug 925361

On 02/02/2012 12:01 PM, Ferdinand @ Camptocamp wrote:
> * a calendar entry must always be in users time zone

Sure, and because calendar entries rely on datetime rather than pure
date values, it is automatically the case already, no change needed.

> * a invoice date must always be in the time zone where it has been
> issued - if different from the users time zone the time zone should
> be displayed / printed to avoid misunderstandings.

Based on your comment, it seems you're in favor of option 2 from the bug
description. Thanks for the feedback.
In the context of option 2, showing the "timezone of the document"
somewhere next to the "frozen" date fields (such as an invoice's date)
would indeed be useful. However storing that information either requires
some rather drastic API changes (such as an entirely new kind of date
storage format), or manual customizations of all the relevant documents.
BTW, we should keep in mind that this problem has always been present in
the past for geographically distributed teams. We can reasonably expect
team members to be quite aware of their timezone difference (they're
working different business hours!), and exert some caution when looking
at documents created by colleagues working in a different world region.
Still, that would be a nice-to-have feature, and a good suggestion for
the future, albeit probably out of scope for 6.1.