Bug 504313 - Cannot move with keyboard to due scheduled transactions beyond multiple instances of one scheduled transaction
Summary: Cannot move with keyboard to due scheduled transactions beyond multiple insta...
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: ux-ui (other bugs)
Version First Reported In: 5.1.3
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-16 07:48 UTC by Ingo Klöcker
Modified: 2025-06-16 03:47 UTC (History)
0 users

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 Ingo Klöcker 2025-05-16 07:48:24 UTC
Moving with keyboard to due scheduled transactions in ledger beyond two instances of the same scheduled transaction is not possible

Sometimes, I don't update a ledger for more than one month. In this case there will be multiple entries of due scheduled transactions for monthly transactions. It's not possible to move with the keyboard to the second entry of a due scheduled transaction. That's okay. But I would expect that pressing Down would skip the not-selectable entries of a due scheduled transaction and jump to the first entry of the next due scheduled transaction.

STEPS TO REPRODUCE
1. Have a scheduled transaction A with at least two due transactions.
2. Have a second scheduled transaction B with a due transaction between the two due transactions of A.
3. Open the ledger.

OBSERVED RESULT
The ledger shows two (or more) entries of A waiting to be inserted into the ledger followed by one (or more) entry of B. OK
With the Down arrow I can select the first entry of A. OK
I cannot select the second entry of A. OK
I cannot use the Down arrow to select the (first) entry of B. Not OK

EXPECTED RESULT
When the first entry of A is selected and I press the Down arrow then the selection should jump to the (first) entry of B.

SOFTWARE/OS VERSIONS
I doubt that this information is relevant. The problem exists since a long time.
Comment 1 Thomas Baumgart 2025-05-17 05:59:47 UTC
This seems to have been addressed in the current development version. Can you confirm that so that we can close this as fixed in 5.2? Thanks.
Comment 2 Bug Janitor Service 2025-06-01 03:47:28 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2025-06-16 03:47:39 UTC
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.