[kmymoney] [Bug 414932] New: Incorrect "opening balance" in daily and weekly "Investment Worth Graph"

[bugzilla_noreply at kde.org]

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

            Bug ID: 414932
           Summary: Incorrect "opening balance" in daily and weekly
                    "Investment Worth Graph"
           Product: kmymoney
           Version: 5.0.7
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: reports
          Assignee: kmymoney-devel at kde.org
          Reporter: zoltan1980 at gmail.com
  Target Milestone: ---

Created attachment 124363
  --> https://bugs.kde.org/attachment.cgi?id=124363&action=edit
KMY file to reproduce error

SUMMARY

The "opening balance" of an "Investment Worth Graph" is calculated using the
latest stock price instead of the stock price in effect at the start of the
report period. Only daily and weekly charts are affected, monthly charts look
correctly.

STEPS TO REPRODUCE
I created a file to demonstrate the problem. It has a single stock with a
starting price of $1 as of Jan 1, 2000, and increasing by $1 every month. There
is a single share of this stock bought in Jan 1, 2000 and no other investment
transaction. Use the attached file and open the Investment Worth Graph report.
You can also switch to the report view to observe incorrect numbers in a table.

OBSERVED RESULT

When ticks are set to be daily (the default) or weekly, the "opening balance"
on the left of the chart shows a value calculated using the latest price (which
in this test file is much higher than expected). This happens regardless of the
time range: please see the attached screenshots that use a range of 1 year (the
default) and 2 years. When the ticks are set to be monthly, the values are
correct.

EXPECTED RESULT

The opening balance should be calculated using the price that was in effect at
the start of the period.

ADDITIONAL INFORMATION

I created the test file and the screenshots using an older version (plus some
manual scripting), but the bug is present in v5.0.7 as well.

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