[kmymoney] [Bug 482426] New: should the transaction filter also look at category?
https://bugs.kde.org/show_bug.cgi?id=482426 Bug ID: 482426 Summary: should the transaction filter also look at category? Classification: Applications Product: kmymoney Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-devel@kde.org Reporter: ostrof...@users.sourceforge.net Target Milestone: --- If you use the transaction filter in an investment or brokerage account, it searches most fields, but not the category. I thought it searched the Security, but that may be just because that string is also in the memo. This would be very useful for me in finding transactions where the category does not match what it should be, based on the memo. (I have "dividends" and "foreign dividends", but no easy way to filter on transaction with just "dividends" in the memo, but "foreign dividends" as the category. I know I can use a transaction search, but I'm hoping for something more streamlined, as this is only ever for one account at a time. -- You are receiving this mail because: You are the assignee for the bug.
question on editing multiple transactions
I'm curious about the current state of editing multiple transactions in the ledger, in master branch. I know there are some restrictions, but I don't remember what they are, or if they are actually written down anywhere. I have several transactions with the same category, which was incorrectly set on OFX import. I can select more than one of these transactions, and select edit, but the category field is disabled. In a 5.1. appimage, I can select and edit multiple transactions, and can set the category dropdown, but am still not able to save the changes (the OK button is disabled.) Thanks for any hints of pointers to why this might be. Jack
[kmymoney] [Bug 482346] Set cursor to start in 'date' field in ledger view
https://bugs.kde.org/show_bug.cgi?id=482346 --- Comment #3 from Thomas Baumgart --- To shed some light on the master version: data entry for transactions will always happen form based in the ledger. The order of the columns has nothing to do with the order of the widget entries. The editor has been completely rewritten and since Jack mentioned "I suppose a further wishlist could be to let the user specify the tab order of fields in the ledger": Pressing Ctrl+Shift+T while in the editor provides just that. Keeping it as resolved in 5.2 -- You are receiving this mail because: You are the assignee for the bug.
