Comment 35 for bug 365065
Revision history for this message
|
|
#35 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I think gnucash saves two timestamps for each transaction, doesn't it. One is the date for the receipt, the other when the transaction was keyed in. While respecting timezone for the latter it makes absolutely *NO* sense for the former. At least as long as gnucash assumes the transaction taking place at midnight which is what happens currently. We don't enter an hour for tx date, why is gnucash trying to be smart about this when it doesn't really have the data accurate up to the hour???
The entered data is only accured up to the date, no need to mess with timezones.