https://bugs.kde.org/show_bug.cgi?id=431300
--- Comment #2 from Jack <ostrof...@users.sourceforge.net> --- Reading my reply now, I realize it wasn't complete accurate in describing things. I apologize for that. Part of the issue is a potential confusion with terminology. Any ownership of a stock (or mutual fund) requires a SECURITY to exist. That contains the basic information about the stock, such as trading symbol, exchange, and source of online quotes. Then, for each Investment Account which owns any of that Security, there does need to be an EQUITY account. That is used to keep the shares owned in that Investment Account separate from shares owned in any other Investment account. One example of the need for this is that the two investment accounts may have different currencies, even if that is not a common occurrence. As you point out, there are some problems with this specific implementation - there is a danger of creating a new SECURITY when adding an EQUITY to an Investment account. Bug 443566 is specifically about making this easier, and less prone to error. The current way also duplicates some information about the stock, which can lead to confusion. The development team is about to start reviewing all open bugs about Investments, and hopefully some of them will be addressed in the coming months. As developer resources are scarce, there is no timetable for this. The process of adding a Security to an Investment Account will certainly be considered, as will whether a separate Equity Account per Investment Account is really necessary. I think it's fair to say that the goals are increased functionality with decreased chances for errors and confusion, but anything which requires major changes to the underlying data structures may end up further deferred. -- You are receiving this mail because: You are the assignee for the bug.
