Bug 213334 - delete splitted transaction - void/unassigned category
Summary: delete splitted transaction - void/unassigned category
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: git (master)
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-05 22:42 UTC by William
Modified: 2017-12-19 07:11 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description William 2009-11-05 22:42:04 UTC
Version:           1.02.42 (using KDE 4.3.3)
OS:                Linux
Installed from:    openSUSE RPMs

When I have a splitted transaction (two or more categories assigned to one transaction) and I wipe or delete the split for one single category - transaction will stay with "void" category (unassigned) and I must enter again category.
Comment 1 Thomas Baumgart 2009-11-06 07:47:20 UTC
Can you explain in more detail how you do this and what you observe? I am unable to duplicate your problem (or I am overseeing something).
Comment 2 William 2009-11-06 10:40:37 UTC
Hi,

In one ledger, enter a new transaction with split fonction, validate it.
Then edit/modify this new transaction and erase all data in box of split fonction. If you define the single category into this split box, I award you that's working perfectly.
But that's not this way to find this little bug. After erase all data, validate. You should have a box for three choices, because there is an amount without category. Then define single category to assign to transaction and validate transaction.
You may have after this, an error on this transaction with "unassigned category".



> Message du 06/11/09 07:47
> De : "Thomas Baumgart" 
> A : asemann@orange.fr
> Copie à : 
> Objet : [Bug 213334] delete splitted transaction - void/unassigned category
> 
> 
> https://bugs.kde.org/show_bug.cgi?id=213334
> 
> 
> Thomas Baumgart  changed:
> 
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |ipwizard@users.sourceforge.
> | |net
> 
> 
> 
> 
> --- Comment #1 from Thomas Baumgart  2009-11-06 07:47:20 ---
> Can you explain in more detail how you do this and what you observe? I am
> unable to duplicate your problem (or I am overseeing something).
> 
> -- 
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
> 
>
Comment 3 Cristian Oneț 2014-08-20 20:31:13 UTC
Moving this wish to kmymoney4.
Comment 4 Cristian Oneț 2014-08-22 06:43:38 UTC
Could you reproduce this with a newer version? I followed your description but did not seen the described issue.
Comment 5 Jack 2017-12-18 22:20:41 UTC
I think either this has been fixed since 1.02, or it was not described well.

The closest I can come is to create a new transaction, select the split icon, and enter amount for two categories.  When you save the transaction, the category shows as "Split transaction."  Edit the transaction again, click the split icon, click "Clear All,"  Click "Continue,"  Click "OK."  Select the third radio button to leave the total amount unchanged, and click  "OK."  The Category still says "Split transaction."  Save the transaction, and now the category switches to "*** UNASSIGNED ***."  This seems correct.  However, this is different from the original report, which says to assign a single category and then save.  If you assign a new category after deleting the splits and before saving the transaction, this works fine.

I wonder if the best resolution is to close as Unsupported, and reopen if someone can actually reproduce it with a current version.
Comment 6 Thomas Baumgart 2017-12-19 07:11:01 UTC
In case the text "Split transaction" appears in the category field and you focus into this field on a transaction with multiple splits, the split transaction editor opens. In the case where the text appears and there is no assignment at all and you focus into the field then the text is all selected and you can enter a category if you wish so.

The new transaction editor does remove the text in this case so it is safe to close it.