Summary: | Investment and Net Worth reports values mutual funds with 1 instead of price | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | Volker Paul <volker.paul> |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | asoliverez, jan_cecile, lukasz.wojnilowicz, onet.cristian, volker.paul |
Priority: | NOR | ||
Version: | 4.5 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Volker Paul
2010-11-14 21:33:02 UTC
Go to Prices, verify you have an actual price entered. (In reply to comment #1) > Go to Prices, verify you have an actual price entered. Yes, you are right. I can enter a price explicitly, additionally, in the price tool. But what I want to say is: I already entered that price. I entered an investment transaction: Activity: Buy shares Security: test Shares: 200 Price/share: 50 Total: 10000 And normally I would expect that price of 50 to be used in reports as the value of that stock until I enter a (new) price. Instead, the Investment Performance by Account report shows: Account Starting Balance Buys ... Return On Investment Amount test 0.00 10,000.00 -98.00% 200.00 Imagine the shock a casual user gets when he sees that he lost almost everything, only to find out after a lot of research that he had to enter the same price twice at different places, once in the transaction and once in the price tool. Ok, he can do that, but computing is all about doing things automatically. So my question is: why not take the purchase price/share automatically into the stored prices list? I can't agree with this being "not a bug" (INVALID). It may be minor ("minor loss of function, or other problem where easy workaround is present"). Entering data twice is a workaround at best. And the example shows that the principle of least surprise (POLS) is violated. (From Wikipedia:) "It states that, when two elements of an interface conflict, or are ambiguous, the behaviour should be that which will least surprise the user; in particular a programmer should try to think of the behavior that will least surprise someone who uses the program, rather than that behavior that is natural from knowing the inner workings of the program." Now when you buy a stock, in reality it first approximately holds its value and the user is surprised if in KMyMoney's reports it suddenly has a completely different value. So this is surely not an ideal situation and requires a workaround. While I can understand that you are too busy to implement it now, I do think this is something a user normally wants to have, so it's at least a wish, a "nice-to-have" feature, as it saves the user extra work. And it's easy to implement. Just open a dialog box asking the user: "Should this price for this security be entered into prices at this date for later reference in reports?" and if the user agrees, insert the price in the list. What do the others think? Have you checked the "Enter prices on entry" setting? (In reply to comment #4) > Have you checked the "Enter prices on entry" setting? No, and I can't find such a setting. Where is it? I sort of remember that we had such a feature. It probably got lost somewhere. On Sunday, December 12, 2010 18:47:40 Thomas Baumgart wrote:
> https://bugs.kde.org/show_bug.cgi?id=256930
>
>
>
>
>
> --- Comment #6 from Thomas Baumgart <ipwizard users sourceforge net>
> 2010-12-12 18:47:39 --- I sort of remember that we had such a feature. It
> probably got lost somewhere.
Thanks for this answer. I already startet to think I'm blind.
So I have to enter the price manually.
Volker
The problem seems to be that the share price is not entered into a price automatically. There is such an option when you deal with foreign currency accounts, but not in the case of investments. I've also seen this - the first time I save after adding an investment, the consistency check says I don't have a price on or before the opening day of the investment. Funny thing is, I don't manually enter one, and it stops complaining. Has it entered one for me automatically, or does it just issue that particular complaint once per investment? That consistency check is performed every time you save, so it is either entered automatically or via online update. That's why I think something is odd. An online update would get a price for the date of the update, not for an earlier date, and I generally enter new investments at the end of the month when I'm getting ready to reconcile. If it's automatic, why doesn't it do it as soon as you create the investment (assuming you do so as part of the process of purchasing shares, where you do provide a price) ? Anyway - should we create a wish-list to automatically enter share prices whenever they are entered in a buy/sell transaction? This should be closed and a wishlist should be entered to have a dialog come up to enter share price, like it's done for foreign currency. I think the value of 1 was chosen, rather arbitrarily, to avoid zero divides. I agree with the request: It is better to have no result (error) than a wrong one. I cannot reproduce it anymore in master branch of KMM. |