Bug 244809 - Adjust split shares of scheduled transaction in foreign currency over time
Summary: Adjust split shares of scheduled transaction in foreign currency over time
Status: RESOLVED FIXED
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR wishlist
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-16 02:08 UTC by Alvaro Soliverez
Modified: 2018-03-01 15:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alvaro Soliverez 2010-07-16 02:08:19 UTC
Version:           unspecified (using KDE 4.4.4) 
OS:                Linux

When a scheduled transaction has splits in multiple currencies, the conversion rate may drift over time.
Currently, this is fixed as of the last time the schedule was edited.
There should be a way to provide adjusted information to the user without the need to periodically edit the schedule and adjust the currency rate.

A possible way is to define a split that will be fixed over the time of the schedule and adjust all other splits based on that split. It should be manually set by the user (but a default split should be proposed, of course)

Then, MyMoneySchedule should provide a method to query the adjusted amount for each split, and other areas of the application should call this new method, as it was done for adjusted due dates.

Reproducible: Always


Actual Results:  
The conversion rate when foreign currencies are involved, are fixed as of the time of last edit of the schedule

Expected Results:  
The conversion rate should update itself over time according to user's choice on which split to use as baseline reference.

This should not be done before stable release, as it could prove to be quite disruptive.
Comment 1 Michael Carpino 2018-03-01 15:20:41 UTC
Enhancement requested over 5 years ago.  Bug closed.