Bug 388012

Summary: Number Field in Scheduled Transaction Dialog
Product: [Applications] kmymoney Reporter: schoenes-rad
Component: generalAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: 4.8.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Documentation: Manual vs. Data Entry Dialog

Description schoenes-rad 2017-12-18 16:20:52 UTC
Created attachment 109441 [details]
Documentation: Manual vs. Data Entry Dialog

My platform is Lubuntu
-Version-
Kernel		: Linux 4.13.0-19-generic (x86_64)
Version		: #22-Ubuntu SMP Mon Dec 4 11:58:07 UTC 2017
C Library		: GNU C Library / (Ubuntu GLIBC 2.26-0ubuntu2) 2.26
Distribution		: Ubuntu 17.10

- The Scheduled Transaction dialog has a "Number" field next to the "Pay To" field which can be entered into.  Although the screen shot in the manual shows the correct nomenclature for that field, the app itself is missing the field description.

- Regardless what is being entered into the Number field on any give Scheduled Transaction, the actual ledger entry later only shows blanks.  I would like to be able to enter transaction types into this field (e.g. EFT for Electronic Fund Transfer) which would show in the Number (No.) column of the ledger.

- nothing follows -
Comment 1 Justin Zobel 2022-11-10 22:32:22 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 schoenes-rad 2022-11-11 12:45:15 UTC
Was reported again in https://bugs.kde.org/show_bug.cgi?id=450965 and since fixed in v. 5.1.3 as per comment there.  Unfortunately the distribution I use now (MX Linux) hasn't updated KMyMoney to anything more recent than 5.1.1 .

Suggest to close this ticket with reference to https://bugs.kde.org/show_bug.cgi?id=450965

Norbert
Comment 3 Thomas Baumgart 2022-11-12 05:53:07 UTC

*** This bug has been marked as a duplicate of bug 450965 ***