Bug 256633

Summary: no update available for shares, it should be possible to have 4 decimals for the # of shares, wrong investment value displayed
Product: [Applications] kmymoney Reporter: Wim <vooren81>
Component: generalAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: RESOLVED WORKSFORME    
Severity: normal CC: onet.cristian
Priority: NOR    
Version: git (master)   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Wim 2010-11-11 22:17:13 UTC
Version:           unspecified (using KDE 4.5.3) 
OS:                Linux

I am having problems with inputting shares:
- I cannot update the value of my shares and be able to see the previous values of my shares
- On my bank account the number of shares is indicated with 4 decimals, KMyMoney cuts the last 2 decimals and rounds the resulting figure. I really would like to able to have the real number of shares which I own displayed
- The displayed investment value is incorrect, also the value displayed on the home page is incorrect.

Reproducible: Always

Steps to Reproduce:
It always happens

Actual Results:  
See details

Expected Results:  
- allow me to update the value of my shares day by day if I want and record the value for each date. The actual value should be the price per share times the last known value of the shares
- It should allow me to input up to 4 decimals when I specify the amount of shares
-it should display the current value (number of shares x latest known value
Comment 1 Cristian OneČ› 2014-08-20 20:31:30 UTC
Moving this wish to kmymoney4.
Comment 2 Cristian OneČ› 2014-08-22 06:50:59 UTC
An investment report should provide you the requested information. As for the precision it can be configured for each investment.
Comment 3 Jack 2015-07-19 14:40:54 UTC
Should this be closed as invalid, since it IS possible to specify the precision for each investment?  I use four decimal places for many of my investments.
Comment 4 Jack 2018-08-30 21:30:24 UTC
Feel free to reopen if you still have this problem with a more recent version.