[kmymoney] [Bug 409614] New: Share price precision incorrectly limited to 4 decimal places

[Tony Bloomfield]

https://bugs.kde.org/show_bug.cgi?id=409614

            Bug ID: 409614
           Summary: Share price precision incorrectly limited to 4 decimal
                    places
           Product: kmymoney
           Version: 5.0.4
          Platform: Compiled Sources
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: kmymoney-devel at kde.org
          Reporter: tonyb.lx at ntlworld.com
  Target Milestone: ---

Created attachment 121380
  --> https://bugs.kde.org/attachment.cgi?id=121380&action=edit
Screenshot4.6

SUMMARY
In 5.0, share prices are rounded to a maximum of 4 decimal places. This is a
regression from 4.6 (don't know about 4.8).

Assume an investment of 5000.00 at a price of 3.146151 = 1589.2435 shares (this
can happen with UK unit trusts aka mutual funds). The investemnt is created
with a Fraction of 10000 and prices precision of 6 decimal places.

Screenshot4.6 shows the transaction entered in 4.6 with a correct total amount
of 5000.00. Screenshot5.0 shows the same transaction imported into 5.0 where
the price has been rounded to 3.1462, and an attempt to enter a similar
transaction where the amount total amount shows as 5000.08 (until you try to
edit it when it changes to 5000.07!).
There seems to be no way to adjust this down to 5000.00 via fees etc, making it
difficult to balance the books.

STEPS TO REPRODUCE
Use the attached kmy file and try to enter a transaction using the above
figures. 

OBSERVED RESULT
As  described above

EXPECTED RESULT
As shown in screenshot4.6.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu Mate19.04
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
The 2 transactions appear in XML as follows:
 <TRANSACTIONS count="2">
  <TRANSACTION commodity="GBP" entrydate="2019-07-01" id="T000000000000000001"
postdate="2019-07-01" memo="">
   <SPLITS>
    <SPLIT price="1/1" account="A000002" shares="-5000/1" number="" id="S0001"
reconcileflag="0" reconciledate="" action="" bankid="" payee="" memo="This
transaction entered in KMM4.6" value="-5000/1"/>
    <SPLIT price="3146151/1000000" account="A000003" shares="3178487/2000"
number="" id="S0002" reconcileflag="0" reconciledate="" action="Buy" bankid=""
payee="" memo="This transaction entered in KMM4.6" value="5000/1"/>
   </SPLITS>
  </TRANSACTION>
  <TRANSACTION commodity="GBP" entrydate="2019-07-07" id="T000000000000000002"
postdate="2019-07-07" memo="">
   <SPLITS>
    <SPLIT price="1/1" account="A000002" shares="-125002/25" number=""
id="S0001" reconcileflag="0" reconciledate="" action="" bankid="" payee=""
memo="" value="-125002/25"/>
    <SPLIT price="15731/5000" account="A000003" shares="3178487/2000" number=""
id="S0002" reconcileflag="0" reconciledate="" action="Buy" bankid="" payee=""
memo="" value="125002/25"/>
   </SPLITS>
  </TRANSACTION>
 </TRANSACTIONS>

-- 
You are receiving this mail because:
You are the assignee for the bug.