Bug 293470 - split operations does not change its payee if payee changed in uplevel operation
Summary: split operations does not change its payee if payee changed in uplevel operation
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.6.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-06 19:36 UTC by molostoff
Modified: 2014-07-28 14:45 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 molostoff 2012-02-06 19:36:48 UTC
Version:           4.6.1 (using KDE 4.8.0) 
OS:                Linux

If you create some operation and provide a payee (first), then define several splits (sub-operations on accounts) for it, then their payee belongs to be the same as in your operation you defined. 

If you later modify your operation with different payee, then payee of splits (sub-operations) stay unchanged, still pointing to old one from that initially created.

This makes a strange situation where full amount of general operation displays for first payee, and the same amount of splits displays for second payee (e.g. on different one)

I dont know if this is a common feature, or just a bug, but sometimes it works somehow.

Reproducible: Didn't try

Steps to Reproduce:
See details

Actual Results:  
Strange

Expected Results:  
Do not know

OS: Linux (x86_64) release 3.0.0-16-server
Compiler: gcc
Comment 1 Cristian Oneț 2014-07-28 14:45:11 UTC
Actually this is the way it should work. After the transaction is created (when the initial data is used) both ends of the transaction (splits from each account) can be edited independently. This is also true for the memo fields.