GnuCash 3.0 initial observations

[John Ralls]

> On Apr 5, 2018, at 8:37 AM, Adrien Monteleone <adrien.monteleone at gmail.com> wrote:
> 
>> 
>> On Apr 5, 2018, at 7:43 AM, Deva - <pobox.deva at outlook.in> wrote:
>> 
>> Hello,
>> 
>> Firstly, thank you all for this new and much awaited version.
>> 
>> I have just installed GC 3.0 on Mac OS High Sierra 10.13.4 and have been browsing through what’s new and what’s improved and these are observations from my initial test run…
>> 
>> 1. When I first moved from 2.6.6 to 2.6.19, I ran into an issue with average cost as a price source on my mutual fund account. See https://bugzilla.gnome.org/show_bug.cgi?id=775368. I thought this was fixed in 3.0, but it doesn’t seem to be. Note, however, that the use case I gave in that bug report earlier has been fixed, but other investment accounts seem to have issues. Upon reviewing the account with the cost issue, only thing I can see is that when a mutual fund account has both purchases and redemptions, the balance sheet report using average cost price source doesn’t report the cost correctly. When there are only purchases, the cost is computed correctly. Is anyone else seeing this problem? I am keen on moving to 3.0 due to other features introduced in this version, but this is keeping me grounded. I can share an account report and the balance sheet report privately to whoever is interested in diagnosing this problem.
>> 
> I think that’s intended behavior of the ‘average cost’ option. (‘cost’ is supposed to only look at buys, not sells, but it in fact, looks at both) You probably want ‘weighted average’ instead. Read over this comment from a bug report on the ‘average cost’ issue: https://bugzilla.gnome.org/show_bug.cgi?id=775368#c4 <https://bugzilla.gnome.org/show_bug.cgi?id=775368#c4>
> 
> This was ‘fixed’ by making ’nearest in time’ the default instead of ‘average cost’.

Not quite. Read the *rest* of the bug, especially https://bugzilla.gnome.org/show_bug.cgi?id=775368#c36 <https://bugzilla.gnome.org/show_bug.cgi?id=775368#c36>. BTW, Deva is well aware of that bug, he wrote comment 35.

Regards,
John Ralls