Bug 426081 - Add support for increasing/decreasing the bank statement number in the number field
Summary: Add support for increasing/decreasing the bank statement number in the number...
Status: REPORTED
Alias: None
Product: kmymoney
Classification: Applications
Component: file (show other bugs)
Version: 4.8.4
Platform: Other All
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-02 00:19 UTC by Ralf Habacker
Modified: 2020-09-22 20:33 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 Ralf Habacker 2020-09-02 00:19:07 UTC
When entering bank statements, there is currently no simple way of increasing or decreasing the current bank statement number and/or the statement page, as is possible with the date field using the + and - keys on the numeric keypad.

STEPS TO REPRODUCE
1. start kmymoney
2. open file
3. enter ledger with transactions having a statement number
4. add new transaction
5. go to number field

OBSERVED RESULT
You must enter a new number - there is no way to use the previously used number and increase it by one.

EXPECTED RESULT
There should be a way to use the previously used number and increase/decrease it  at least by one.

SOFTWARE/OS VERSIONS
Windows: Windows 10
KDE Frameworks Version: 4.14
Qt Version: 4.8.7

ADDITIONAL INFORMATION
Such support would reduce the number of keystrokes required to enter bank statements.
Comment 1 Thomas Baumgart 2020-09-02 09:57:11 UTC
Does the "Auto increment check number" feature not do just that?

https://docs.kde.org/stable5/en/extragear-office/kmymoney/details.settings.register.html#details.settings.register.dataentry
Comment 2 Ralf Habacker 2020-09-02 12:53:00 UTC
(In reply to Thomas Baumgart from comment #1)
> Does the "Auto increment check number" feature not do just that?
> 
> https://docs.kde.org/stable5/en/extragear-office/kmymoney/details.settings.
> register.html#details.settings.register.dataentry

No, check numbers are individual numbers that are incremented with each new transaction, while statement numbers have a different format, e.g. <statement number>.<statement page>. 

Here is a list of formats supported by kmymoney:
  //                   1.1
  //                   4.5
  //                   4/2018.1
  //                   1,1
  //                   4,5
  //                   4/2018,1

They are only increased in smaller intervals, since a page usually contains several transactions.
Comment 3 Jack 2020-09-02 16:51:56 UTC
Apologies if I'm missing something obvious, but where in the application do these statement and page numbers appear?  I don't recall them, and cannot find any reference in the handbook.
Comment 4 Thomas Baumgart 2020-09-02 18:50:06 UTC
It seems that some people 'abuse' the number field to store the statement number/page information. And for those is the request.
Comment 5 Ralf Habacker 2020-09-03 10:13:24 UTC
(In reply to Jack from comment #3)
> Apologies if I'm missing something obvious, but where in the application do
> these statement and page numbers appear?

In the ledger view and reports - and is used as a reference to the account statement.
Comment 6 Ralf Habacker 2020-09-03 10:18:32 UTC
(In reply to Thomas Baumgart from comment #4)
> It seems that some people 'abuse' the number field to store the statement
> number/page information. And for those is the request.

The current point of view to only provides check numbers in the number field seems to be a bit limited.

gnucash for example documents the number field as "reference", for example check or invoice numbers. 

In a cash book this can be a document number for an invoice or similar or for a bank account the bank statement number.
Comment 7 Jack 2020-09-03 14:09:23 UTC
Thanks both for the info.  The main issue is that you are talking about the existing field, currently called "check number" (or some variant).  I was just trying to confirm that there wasn't a completely separate field I didn't know about.  I have no problem with extending the use of the field - but would need to address those enhancements in the docs, if they ever get applied to 5.x.
Comment 8 Bug Janitor Service 2020-09-18 04:33:13 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Jack 2020-09-22 20:33:07 UTC
Sorry if I'm wrong, but I think the question was answered, so changing back to REPORTED.